Hello, I recollect a "ZMirror" product that was used to "create a filesystem static html mirror of a zope site". <http://www.zope.org/Members/rossl/ZMirror> I downloaded a copy back in September. I don't know if it works with the present Zope versions, though. A static snapshot export option within the Zope admin UI would be great. It could be used with ZScheduler to schedule static backups/archives. Cheers. Alexandre At 07:13 16/05/2000 -0700, zope-admin@zope.org wrote:
From: Shane Hathaway <shane@digicool.com> To: Steve Alexander <s.alexander@lancaster.ac.uk> CC: Christian Scholz <cs@comlounge.net>, zope@zope.org Subject: Re: [Zope] subfolder wrong absolute_url
Steve Alexander wrote:
Perhaps the best sort of tool for taking a "snapshot" of a Zope instance would be a Zope Product that is given a root URL, and returns a .tar.gz of the directory structure and files in that snapshot.
That's an excellent suggestion that could be taken a little further: make "static snapshot" a new option on the "export" screen. It would simply create a .tar.gz.
I wish I had time to do it myself. It would be pretty easy. But now I have other projects I need to do... any takers?
Shane
Alexandre Ratti wrote:
Hello,
I recollect a "ZMirror" product that was used to "create a filesystem static html mirror of a zope site".
<http://www.zope.org/Members/rossl/ZMirror>
I downloaded a copy back in September. I don't know if it works with the present Zope versions, though.
A static snapshot export option within the Zope admin UI would be great. It could be used with ZScheduler to schedule static backups/archives.
Perhaps it could be used to get a rough idea of disk-usage on a per-domain basis as well. Snapshot the domain's folder to the filesystsem, and measure disk usage form there. At least it's a start?
Alex, Do you haev ZScehduler working? cheers, Chris
Alexandre Ratti wrote:
Nope, I haven't installed it yet. I remember reading on the zope-dev list that it's supposed to work though some issues are still unsolved.
I was under the impression that thos issues prevented it from working. :( Let me know if this isn't the case :-) cheers, Chris
What sort of scheduling options would be "nice to have" in a scheduling product? Day of week, time of day, every x minutes/hours, what else?
Karl Lewin wrote:
What sort of scheduling options would be "nice to have" in a scheduling product?
1. The ability to have a method called at a certain DateTime eg: next Tuesday, at 5pm GMT 2. The ability to have a method executed every x, where x is a period of time. eg: every 2 hours 3. The ability to have a method executed every x, starting and y and finished at z, where x is a period of time, y is a DateTime object and z is a DateTime object that may be omitted if the process is nto to terminate. eg: every Tuesday at 4pm, starting May 20th, ending December 31st every Wednesday at 5pm GMT from now onwards. Obviously the more flexible the expression of time periods and dates, especially in the last option (for example: every other Tuesday starting today and ending next week would be nice ;-), the better :-) cheers, Chris
You can try out ZScheduler on Windows (I tested on Win98). It actually runs the scheduled tasks. However, because the inter-thread communication isn't working, it degrades to polling the schedule table. The product provides a simple mechanism for rescheduling an event, but does not implement rescheduling policy. The Scheduled Event class is intended for subclassing. In derived classes, you can implement any desired policy for rescheduling events. http://www.zope.org/Members/lstaffor/ZScheduler -- Loren
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Chris Withers Sent: Wednesday, May 17, 2000 05:40 To: Karl Lewin Cc: zope@zope.org Subject: Re: [Zope] ZScheduler
Karl Lewin wrote:
What sort of scheduling options would be "nice to have" in a scheduling product?
1. The ability to have a method called at a certain DateTime eg: next Tuesday, at 5pm GMT
2. The ability to have a method executed every x, where x is a period of time. eg: every 2 hours
3. The ability to have a method executed every x, starting and y and finished at z, where x is a period of time, y is a DateTime object and z is a DateTime object that may be omitted if the process is nto to terminate. eg: every Tuesday at 4pm, starting May 20th, ending December 31st every Wednesday at 5pm GMT from now onwards.
Obviously the more flexible the expression of time periods and dates, especially in the last option (for example: every other Tuesday starting today and ending next week would be nice ;-), the better :-)
cheers,
Chris
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In article <000101bfc01a$1ec3e2e0$8b0127d8@icompression.com>, Loren Stafford <lstafford@icompression.com> writes
You can try out ZScheduler on Windows (I tested on Win98). It actually runs the scheduled tasks. However, because the inter-thread communication isn't working, it degrades to polling the schedule table.
I tried this out on my notebook running NTWK4.0 and got this from the log Failed to trigger event. Type=exceptions.AttributeError Val=this (File: D:\zope2\lib\python\Products\MailHost\SendMailTag.py Line: 188) 500 Internal Server Error for http://a7800nt:8080/myfolder/cron/trigger - ------ 2000-05-20T05:40:24 PROBLEM(100) Products.ZScheduler.Loggerr Failed to disarm event The DTML code just sends an email, and works fine when tested outside the ZEvent. - -- Regards, Graham Chiu gchiu<at>compkarori.co.nz http://www.compkarori.co.nz/index.php Powered by Interbase and Zope -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 iQA/AwUBOSWAcbTRdIWzaLpMEQLcVwCfSFs3pOY8mL9Q0lXp+uAzY9oXLZwAn1d6 hRJQjCo9t/yt4wdMXWqDiep0 =mBSf -----END PGP SIGNATURE-----
What happens when you execute the event's "trigger" method from the browser's location line? e.g. http://my.site.dom/my_scheduled_method/trigger -- Loren
In article <000101bfc01a$1ec3e2e0$8b0127d8@icompression.com>, Loren Stafford <lstafford@icompression.com> writes
You can try out ZScheduler on Windows (I tested on Win98). It actually
runs
the scheduled tasks. However, because the inter-thread communication isn't working, it degrades to polling the schedule table.
I tried this out on my notebook running NTWK4.0 and got this from the log
Failed to trigger event. Type=exceptions.AttributeError Val=this (File: D:\zope2\lib\python\Products\MailHost\SendMailTag.py Line: 188) 500 Internal Server Error for http://a7800nt:8080/myfolder/cron/trigger - ------ 2000-05-20T05:40:24 PROBLEM(100) Products.ZScheduler.Loggerr Failed to disarm event
The DTML code just sends an email, and works fine when tested outside the ZEvent.
- -- Regards, Graham Chiu gchiu<at>compkarori.co.nz http://www.compkarori.co.nz/index.php Powered by Interbase and Zope
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In article <001901bfc360$6e3f9280$2101a8c0@pavilion>, Loren Stafford <lstaffor@dynalogic.com> writes
What happens when you execute the event's "trigger" method from the browser's location line?
Works fine. - -- Regards, Graham Chiu gchiu<at>compkarori.co.nz http://www.compkarori.co.nz/index.php Powered by Interbase and Zope -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 iQA/AwUBOSe0JbTRdIWzaLpMEQKKbACdGc5oaSRM/ylOkfKu+T1K2omraewAoK8F eEoeBaR7+nqt1/N69Fo4SYqD =lKwU -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In article <001901bfc360$6e3f9280$2101a8c0@pavilion>, Loren Stafford <lstaffor@dynalogic.com> writes
What happens when you execute the event's "trigger" method from the browser's location line?
Perhaps this will help. Here's my Zevent <dtml-var zMailTest> And here's zMailTest which works fine when called from the browser: <dtml-sendmail smtphost="mail.netlink.net.nz"> To: GC <anon_emouse@hotmail.com> From: TV time <reminder@compkarori.co.nz> Subject: This is cron test Charmed is on tonight at 7 pm. </dtml-sendmail> And here is the log report. Isn't 503 an SMTP error of some sort? 2000-05-21T22:48:10 PROBLEM(100) Products.ZScheduler.Loggerr Trigger event: http://a7800nt:8080/zTV Trigger time: 2000/05/22 10:48:00 GMT+12 Failed to trigger event. Type=exceptions.KeyError Val=<META HTTP-EQUIV="Pragma" CONTENT="no-cache"> <META HTTP- EQUIV="Expires" CONTENT="0"> <HTML><HEAD><TITLE>zTV</TITLE></HEAD><BODY BGCOLOR="#FFFFFF"> <table width="100%" border=0 cellspacing="0" cellpadding="0" bgcolor="#000000"> <tr> <td h (File: d:\zope2\lib\python\DocumentTemplate\DT_String.py Line: 502) 503 Service Unavailable for http://a7800nt:8080/zTV/trigger - ------ 2000-05-21T22:48:10 PROBLEM(100) Products.ZScheduler.Loggerr Failed to disarm event - -- Regards, Graham Chiu gchiu<at>compkarori.co.nz http://www.compkarori.co.nz/index.php Powered by Interbase and Zope -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 iQA/AwUBOSfA6LTRdIWzaLpMEQJCGACg39opsy130qgjwfFNS5kFUAHGAyMAoPTO Fe2zVB6LB3QOX773fJ2NbbsO =Kq9S -----END PGP SIGNATURE-----
Graham, Thanks for sending all the info. I haven't had a chance to check it all out. But I want to ask one more thing: did you install the patch to client.py as mentioned in CHANGES.txt and http://www.zope.org/Members/lstaffor/ZScheduler/ZSchedulerWiki/BugReports ? -- Loren ----- Original Message ----- From: "Graham Chiu" <anon_emouse@hotmail.com> To: <zope@zope.org> Sent: May 21, 2000 02:56 PM Subject: Re: [Zope] ZScheduler
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
In article <001901bfc360$6e3f9280$2101a8c0@pavilion>, Loren Stafford <lstaffor@dynalogic.com> writes
What happens when you execute the event's "trigger" method from the browser's location line?
Perhaps this will help.
Here's my Zevent
<dtml-var zMailTest>
And here's zMailTest which works fine when called from the browser:
<dtml-sendmail smtphost="mail.netlink.net.nz"> To: GC <anon_emouse@hotmail.com> From: TV time <reminder@compkarori.co.nz> Subject: This is cron test
Charmed is on tonight at 7 pm.
</dtml-sendmail>
And here is the log report. Isn't 503 an SMTP error of some sort?
2000-05-21T22:48:10 PROBLEM(100) Products.ZScheduler.Loggerr Trigger event: http://a7800nt:8080/zTV Trigger time: 2000/05/22 10:48:00 GMT+12 Failed to trigger event. Type=exceptions.KeyError Val=<META HTTP-EQUIV="Pragma" CONTENT="no-cache"> <META HTTP- EQUIV="Expires" CONTENT="0"> <HTML><HEAD><TITLE>zTV</TITLE></HEAD><BODY BGCOLOR="#FFFFFF"> <table width="100%" border=0 cellspacing="0" cellpadding="0" bgcolor="#000000"> <tr> <td h (File: d:\zope2\lib\python\DocumentTemplate\DT_String.py Line: 502) 503 Service Unavailable for http://a7800nt:8080/zTV/trigger - ------ 2000-05-21T22:48:10 PROBLEM(100) Products.ZScheduler.Loggerr Failed to disarm event
- -- Regards, Graham Chiu gchiu<at>compkarori.co.nz http://www.compkarori.co.nz/index.php Powered by Interbase and Zope
-----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1
iQA/AwUBOSfA6LTRdIWzaLpMEQJCGACg39opsy130qgjwfFNS5kFUAHGAyMAoPTO Fe2zVB6LB3QOX773fJ2NbbsO =Kq9S -----END PGP SIGNATURE-----
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
In article <019501bfc6c2$91e19b60$2101a8c0@pavilion>, Loren Stafford <lstaffor@dynalogic.com> writes
Graham,
Thanks for sending all the info. I haven't had a chance to check it all out. But I want to ask one more thing: did you install the patch to client.py as mentioned in CHANGES.txt and http://www.zope.org/Members/lstaffor/ZScheduler/ZSchedulerWiki/BugReports
Loren, Since this bug referenced a reschedule operation, I didn't bother to apply the patch - should I? -- Regards, Graham Chiu gchiu<at>compkarori.co.nz http://www.compkarori.co.nz/index.php Powered by Interbase and Zope
Yes. The Client.py patch must be applied for any use of ZScheduler, if the server is not listening on the default port. "reschedule" is always called when an event is triggered, so that there is an opportunity to reschedule or disarm the event. If "reschedule" fails (as it will if the server is not on the default port and the patch is not applied), the whole transaction fails. By the way, what version of Zope are you using? I reported the bug in version 2.1.4. I wonder (because I haven't checked yet) if it was fixed in later versions. -- Loren ----- Original Message ----- From: "Graham Chiu" <anon_emouse@hotmail.com> To: <zope@zope.org> Sent: May 25, 2000 11:11 PM Subject: Re: [Zope] ZScheduler
In article <019501bfc6c2$91e19b60$2101a8c0@pavilion>, Loren Stafford <lstaffor@dynalogic.com> writes
Graham,
Thanks for sending all the info. I haven't had a chance to check it all out. But I want to ask one more thing: did you install the patch to client.py as mentioned in CHANGES.txt and http://www.zope.org/Members/lstaffor/ZScheduler/ZSchedulerWiki/BugReports
Loren,
Since this bug referenced a reschedule operation, I didn't bother to apply the patch - should I?
-- Regards, Graham Chiu gchiu<at>compkarori.co.nz http://www.compkarori.co.nz/index.php Powered by Interbase and Zope
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In article <001301bfc731$2af9c480$2101a8c0@pavilion>, Loren Stafford <lstaffor@dynalogic.com> writes
Yes. The Client.py patch must be applied for any use of ZScheduler, if the server is not listening on the default port.
The default port in Zope is 8080, whereas I recall seeing the bug applies if not on 80.
"reschedule" is always called when an event is triggered, so that there is an opportunity to reschedule or disarm the event. If "reschedule" fails (as it will if the server is not on the default port and the patch is not applied), the whole transaction fails.
Except that I scheduled a non-smtp event which worked fine without the patch.
By the way, what version of Zope are you using? I reported the bug in version 2.1.4. I wonder (because I haven't checked yet) if it was fixed in later versions.
Well, it's clear I need to install this patch and try again. I'm using 2.1.4. - -- Regards, Graham Chiu gchiu<at>compkarori.co.nz http://www.compkarori.co.nz/index.php Powered by Interbase and Zope -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 iQA/AwUBOS4xebTRdIWzaLpMEQIPWwCg5uZpGCphTW2SAnYt0nHBQ6m5IgsAn2xW 4n4onec3rtzBnz9ZB3SRmuzc =5YOQ -----END PGP SIGNATURE-----
You're right. I should have said port 80 instead of default port. I was thinking of the system "default" for HTTP which is 80. In any case you need the patch. -- Loren ----- Original Message ----- From: "Graham Chiu" <anon_emouse@hotmail.com> To: <zope@zope.org> Sent: May 26, 2000 12:10 PM Subject: Re: [Zope] ZScheduler
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
In article <001301bfc731$2af9c480$2101a8c0@pavilion>, Loren Stafford <lstaffor@dynalogic.com> writes
Yes. The Client.py patch must be applied for any use of ZScheduler, if the server is not listening on the default port.
The default port in Zope is 8080, whereas I recall seeing the bug applies if not on 80.
"reschedule" is always called when an event is triggered, so that there
is
an opportunity to reschedule or disarm the event. If "reschedule" fails (as it will if the server is not on the default port and the patch is not applied), the whole transaction fails.
Except that I scheduled a non-smtp event which worked fine without the patch.
By the way, what version of Zope are you using? I reported the bug in version 2.1.4. I wonder (because I haven't checked yet) if it was fixed
in
later versions.
Well, it's clear I need to install this patch and try again. I'm using 2.1.4.
- -- Regards, Graham Chiu gchiu<at>compkarori.co.nz http://www.compkarori.co.nz/index.php Powered by Interbase and Zope
-----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1
iQA/AwUBOS4xebTRdIWzaLpMEQIPWwCg5uZpGCphTW2SAnYt0nHBQ6m5IgsAn2xW 4n4onec3rtzBnz9ZB3SRmuzc =5YOQ -----END PGP SIGNATURE-----
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Chris Withers wrote:
Karl Lewin wrote:
What sort of scheduling options would be "nice to have" in a scheduling product?
1. The ability to have a method called at a certain DateTime eg: next Tuesday, at 5pm GMT
2. The ability to have a method executed every x, where x is a period of time. eg: every 2 hours
3. The ability to have a method executed every x, starting and y and finished at z, where x is a period of time, y is a DateTime object and z is a DateTime object that may be omitted if the process is nto to terminate. eg: every Tuesday at 4pm, starting May 20th, ending December 31st every Wednesday at 5pm GMT from now onwards.
Obviously the more flexible the expression of time periods and dates, especially in the last option (for example: every other Tuesday starting today and ending next week would be nice ;-), the better :-)
I would add: something along the lines of: every first and third tuesday of the month. To this list.
Chris Withers wrote:
Karl Lewin wrote:
What sort of scheduling options would be "nice to have" in a scheduling product?
1. The ability to have a method called at a certain DateTime eg: next Tuesday, at 5pm GMT
2. The ability to have a method executed every x, where x is a period of time. eg: every 2 hours
3. The ability to have a method executed every x, starting and y and finished at z, where x is a period of time, y is a DateTime object and z is a DateTime object that may be omitted if the process is nto to terminate. eg: every Tuesday at 4pm, starting May 20th, ending December 31st every Wednesday at 5pm GMT from now onwards.
Obviously the more flexible the expression of time periods and dates, especially in the last option (for example: every other Tuesday starting today and ending next week would be nice ;-), the better :-)
I would add: something along the lines of: every first and third tuesday of the month. To this list.
I would add the "last day of the month" as well. All my best, Jason Spisak CIO HireTechs.com 6151 West Century Boulevard Suite 900 Los Angeles, CA 90045 P. 310.665.3444 F. 310.665.3544 Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.
In article <20000518154034.11612.qmail@mail.hiretechs.com>, Jason Spisak <444@hiretechs.com> writes
I would add the "last day of the month" as well.
All my best,
Or, how about, only if there is no activity on the web server between certain hours, then start doing something... -- Regards, Graham Chiu gchiu<at>compkarori.co.nz http://www.compkarori.co.nz/index.php Powered by Interbase and Zope
Any ideas how to automatically determine whether "now and for the next N minutes is a time period of little activity" from historical or real-time data? -- Loren ----- Original Message ----- From: Graham Chiu <anon_emouse@hotmail.com> To: <zope@zope.org> Sent: May 19, 2000 07:06 PM Subject: Re: [Zope] ZScheduler
In article <20000518154034.11612.qmail@mail.hiretechs.com>, Jason Spisak <444@hiretechs.com> writes
I would add the "last day of the month" as well.
All my best,
Or, how about, only if there is no activity on the web server between certain hours, then start doing something...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In article <001301bfc35f$959f0780$2101a8c0@pavilion>, Loren Stafford <lstaffor@dynalogic.com> writes
Any ideas how to automatically determine whether "now and for the next N minutes is a time period of little activity" from historical or real-time data?
-- Loren
Read the Zserver logs? - -- Regards, Graham Chiu gchiu<at>compkarori.co.nz http://www.compkarori.co.nz/index.php Powered by Interbase and Zope -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 iQA/AwUBOSeddLTRdIWzaLpMEQIxAQCdGG10NP24JJyRhy+09G77XwEenJwAoJ/H IfcllPWWjgD19CWeGiaNpf9k =HV7X -----END PGP SIGNATURE-----
participants (8)
-
Alexandre Ratti -
Bill Anderson -
Chris Withers -
Graham Chiu -
Jason Spisak -
Karl Lewin -
Loren Stafford -
Loren Stafford