[Zope-PAS] Re: new beta
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Janko Hauser wrote: Would it be possible to have a short announcment before a new beta of PAS is done? I know, it is my fault to not have generated a ticket for the domain_auth bug, but a little heads up would perhaps help to get more input. I just tagged one, largely because I need to have a particular feature set released for a client. I have no problems with either: - Fixing your bug before the 1.4 release, assuming the fix is not risky feeling. - Doing another beta, if it is. Please *do* generate the issue in any case. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE16/j+gerLs4ltQ4RAq34AJ9XnLk8PYwXqE8jJgG7Nz7jSVfpQACgsZXj lpMHEVmN5YDQzOwjBGadLdA= =yTwT -END PGP SIGNATURE- ___ Zope-PAS mailing list Zope-PAS@zope.org http://mail.zope.org/mailman/listinfo/zope-pas
[Zope] Zope 2.9 Product Refreshing
Hi. I've been attempting to develop products with Zope 2.9, and am finding it increasingly difficult and slow to do so as Product refreshing no longer works. Google shows up a few results from mailing lists with somewhat negative responses (The gist I'm getting is that no-one 'in the know' wants to worry about fixing it, as they don't see a real need for it). However, as a zope restart seems to take a good 5-10 seconds on my high end workstation (AthlonX2 4800+) with all the essentiall products installed (Plone, archetypes etc, plus my application), it's starting to become a major problem. as an example, I spent about three hours today debugging a problem, 90% of which was wasted waiting for zope restarts after making small changes and adding trace print statements. If I was able to refresh the product I would likely have taken less than half an hour. Another major issue I've discovered is Zope hosting. We reguarly deploy custom sites on shared zope environments, and having to restart an entire server just to update one product severely breaks our uptime guarentee. I'm afraid we are going to have no choice but to either drop back to Zope 2.8, or ditch Zope entirely- something I'd prefer not to have to do with our large codebase. I'm hoping I can garner some support to get the zope developers to fix the problem. Failing that, ANY information pointing me in the right direction would be helpful, as I'm more than happy to fix it myself and submit a patch. If anyone else is finding this a problem, please reply in this thread. :-) Thanks in advance. James. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
--On 7. August 2006 21:47:37 +1000 James Davies [EMAIL PROTECTED] wrote: Hi. I've been attempting to develop products with Zope 2.9, and am finding it increasingly difficult and slow to do so as Product refreshing no longer works. Google shows up a few results from mailing lists with somewhat negative responses (The gist I'm getting is that no-one 'in the know' wants to worry about fixing it, as they don't see a real need for it). Refreshing was always a hack and never something I would call a feature. It was always a hack for *development* purposes but not for production. However, as a zope restart seems to take a good 5-10 seconds on my high end workstation (AthlonX2 4800+) with all the essentiall products installed (Plone, archetypes etc, plus my application), it's starting to become a major problem. You might blame Plone for shipping for three tons of frameworks? as an example, I spent about three hours today debugging a problem, 90% of which was wasted waiting for zope restarts after making small changes and adding trace print statements. If I was able to refresh the product I would likely have taken less than half an hour. I understand and fully agree with you but things are as they are. Even worserRefresh does not work Five... Another major issue I've discovered is Zope hosting. We reguarly deploy custom sites on shared zope environments, and having to restart an entire server just to update one product severely breaks our uptime guarentee. Refresh only works in debug-mode. You want to tell us that you are running a production site in debug-mode? I'm afraid we are going to have no choice but to either drop back to Zope 2.8, or ditch Zope entirely- something I'd prefer not to have to do with our large codebase. I'm hoping I can garner some support to get the zope developers to fix the problem. Failing that, ANY information pointing me in the right direction would be helpful, as I'm more than happy to fix it myself and submit a patch. Dieter Maurer wrote a RefreshTool product lately (not sure if this would solve your problem and not sure if he released it). I doubt that the Refresh situation will change in the near future. -aj pgpfKUIU52Y3N.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
On Mon, Aug 07, 2006 at 09:47:37PM +1000, James Davies wrote: Another major issue I've discovered is Zope hosting. We reguarly deploy custom sites on shared zope environments, and having to restart an entire server just to update one product severely breaks our uptime guarentee. If you use a ZEO setup you can restart the ZEO clients one-by-one. Works for me without downtime... -- __ Nothing is as subjective as reality Reinoud van Leeuwen[EMAIL PROTECTED] http://www.xs4all.nl/~reinoud __ ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
On 8/7/06, Andreas Jung [EMAIL PROTECTED] wrote: Refreshing was always a hack and never something I would call a feature.It was always a hack for *development* purposes but not for production. Yes, but it's still very handy and many people have come to rely on it. You might blame Plone for shipping for three tons of frameworks? I'd agree with you there- theres a little too much bloat, but theres not much that can be done about it at this point without a major architecture update. I understand and fully agree with you but things are as they are. EvenworserRefresh does not work Five... How come? Is there a major technical reason why it CANT work, or is it something thats just broken and needs fixing. I'm happy to do the fixing if it comes to that, I just need someone to point me in the right direction. Refresh only works in debug-mode. You want to tell us that you are runninga production site in debug-mode? No. I've never had a problem refreshing in production mode ? Dieter Maurer wrote a RefreshTool product lately (not sure if this wouldsolve your problem and not sure if he released it). I'll have a look- thanks. I doubt that the Refresh situation will change in the near future. As above- is this a major technical problem with Zope 2.9 or Five, or just something that no-one is really bothered to fix? Thanks, James. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
We have Zeo, but running a seperate instance of zope for each site is still too much (We probably host around 50 sites at the moment, and growing. The only economical way to do this is to put multiple sites in one zope instance).On 8/7/06, Reinoud van Leeuwen [EMAIL PROTECTED] wrote: On Mon, Aug 07, 2006 at 09:47:37PM +1000, James Davies wrote: Another major issue I've discovered is Zope hosting. We reguarly deploy custom sites on shared zope environments, and having to restart an entire server just to update one product severely breaks our uptime guarentee.If you use a ZEO setup you can restart the ZEO clients one-by-one. Worksfor me without downtime...--__ Nothing is as subjective as realityReinoud van Leeuwen[EMAIL PROTECTED]http://www.xs4all.nl/~reinoud _Zope maillist-Zope@zope.org http://mail.zope.org/mailman/listinfo/zope** No cross posts or HTML encoding!**(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
On Mon, Aug 07, 2006 at 10:12:42PM +1000, James Davies wrote: We have Zeo, but running a seperate instance of zope for each site is still too much (We probably host around 50 sites at the moment, and growing. The only economical way to do this is to put multiple sites in one zope instance). Still you can shutdown 1 ZEO client; update products there and start it up again... There will be some performance degradation but the sites stay up... (and I hope you've got enough ZEO clients so that bringing 1 down will not cause severe problems...) -- __ Nothing is as subjective as reality Reinoud van Leeuwen[EMAIL PROTECTED] http://www.xs4all.nl/~reinoud __ ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
--On 7. August 2006 22:08:04 +1000 James Davies [EMAIL PROTECTED] wrote: On 8/7/06, Andreas Jung [EMAIL PROTECTED] wrote: Refreshing was always a hack and never something I would call a feature. It was always a hack for *development* purposes but not for production. Yes, but it's still very handy and many people have come to rely on it. You might blame Plone for shipping for three tons of frameworks? I'd agree with you there- theres a little too much bloat, but theres not much that can be done about it at this point without a major architecture update. As Reinoud pointed out: you might think about your architecture and use multiple ZEO clients + load balancing. I understand and fully agree with you but things are as they are. Even worserRefresh does not work Five... How come? Is there a major technical reason why it CANT work, or is it something thats just broken and needs fixing. I'm happy to do the fixing if it comes to that, I just need someone to point me in the right direction. Refresh only works in debug-mode. You want to tell us that you are running a production site in debug-mode? No. I've never had a problem refreshing in production mode ? Afaik Refresh is not available when running in debug-mode... As above- is this a major technical problem with Zope 2.9 or Five, or just something that no-one is really bothered to fix? Everything is a technical problem :-) E.g. Zope 3 browser views (except page templates) can not be refreshed..so you have at least one Zope 3 issue -aj pgpRI3OWyxCWG.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: Zope 2.9 Product Refreshing
Andreas Jung wrote: James Davies wrote: Another major issue I've discovered is Zope hosting. We reguarly deploy custom sites on shared zope environments, and having to restart an entire server just to update one product severely breaks our uptime guarentee. Refresh only works in debug-mode. You want to tell us that you are running a production site in debug-mode? Since when does refresh only work in debug mode? Admittedly we are still on Zope 2.7.x, but it works in non-debug mode for me. When I need to update skin folders on our production server then I do that by forcing the skin product to refresh. For other products I restart the servers, but as Reinoud points out if you have multiple ZEO clients that doesn't result in any downtime (we currently have 6 ZEO clients) although it will result in a slower response for the first few hits after the restart. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: Zope 2.9 Product Refreshing
--On 7. August 2006 12:42:38 + Duncan Booth [EMAIL PROTECTED] wrote: Andreas Jung wrote: James Davies wrote: Another major issue I've discovered is Zope hosting. We reguarly deploy custom sites on shared zope environments, and having to restart an entire server just to update one product severely breaks our uptime guarentee. Refresh only works in debug-mode. You want to tell us that you are running a production site in debug-mode? Since when does refresh only work in debug mode? Admittedly we are still on Zope 2.7.x, but it works in non-debug mode for me. Possibly I haven't used Refresh since Zope 2.7 :-) I considered it always to be a hack and it raised more problems than it solved. -aj pgpuLRRQR3Tis.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] ZEO Problem Clients Waiting
HI, we have quite a Problem with out Zope/Zeo system. We run at the moment Zope cluster with 10 application servers and a zeo server with Filestorage. Our Data.fs is 3.5 Gig at the moment (after Pack). I runs most of the time without problem. But sometimes things screw up 2006-08-07T14:29:19 INFO ZEO.StorageServer (97002/10.152.64.23:52518) Transaction +blocked waiting for storage. Clients waiting: 1. 2006-08-07T14:29:29 INFO ZEO.StorageServer (97002/10.152.64.18:60205) Transaction +blocked waiting for storage. Clients waiting: 2. 2006-08-07T14:29:39 INFO ZEO.StorageServer (97002/10.152.64.19:55021) Transaction +blocked waiting for storage. Clients waiting: 3. 2006-08-07T14:29:39 INFO ZEO.StorageServer (97002/10.152.64.15:62775) Transaction +blocked waiting for storage. Clients waiting: 4. 2006-08-07T14:29:41 INFO ZEO.StorageServer (97002/10.152.64.22:59407) Transaction +blocked waiting for storage. Clients waiting: 5. 2006-08-07T14:29:41 INFO ZEO.StorageServer (97002/10.152.64.20:51153) Transaction blocked waiting for storage. Clients waiting: 6. 2006-08-07T14:29:41 INFO ZEO.StorageServer (97002/10.152.64.21:52951) Transaction blocked waiting for storage. Clients waiting: 7. 2006-08-07T14:29:41 INFO ZEO.StorageServer (97002/10.152.64.14:53919) Transaction blocked waiting for storage. Clients waiting: 8. 2006-08-07T14:29:41 INFO ZEO.StorageServer (97002/10.152.64.17:54463) Transaction blocked waiting for storage. Clients waiting: 9. 2006-08-07T14:29:47 INFO ZEO.StorageServer (97002/10.152.64.16:53743) Blocked transaction restarted. Clients waiting: 8 2006-08-07T14:29:47 INFO ZEO.StorageServer (97002/10.152.64.23:52518) Blocked transaction restarted. Clients waiting: 7 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.23:52518) Transaction blocked waiting for storage. Clients waiting: 8. 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.18:60205) Blocked transaction restarted. Clients waiting: 7 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.19:55021) Blocked transaction restarted. Clients waiting: 6 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.15:62775) Blocked transaction restarted. Clients waiting: 5 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.22:59407) Blocked transaction restarted. Clients waiting: 4 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.20:51153) Blocked transaction restarted. Clients waiting: 3 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.21:52951) Blocked transaction restarted. Clients waiting: 2 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.16:53743) Transaction blocked waiting for storage. Clients waiting: 3. 2006-08-07T14:29:49 INFO ZEO.StorageServer (97002/10.152.64.14:53919) Blocked transaction restarted. Clients waiting: 2 2006-08-07T14:29:50 INFO ZEO.StorageServer (97002/10.152.64.17:54463) Blocked transaction restarted. Clients waiting: 1 2006-08-07T14:29:50 INFO ZEO.StorageServer (97002/10.152.64.23:52518) Blocked transaction restarted. This one was a very quick one only 30 seconds. I have Blocked Transaktion that ware waiting for more than 2 minutes. When there a 9 Clients waiting our complete Zopesite comes to a halt until the transaction is restarted. As im not realy deep in the ZODB/ZEO subject. Can anybody pinpoint me where to look for the Problem. Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpngdBFhioow.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: Zope 2.9 Refreshing
James Davies wrote: [snip] I'm hoping I can garner some support to get the zope developers to fix the problem. Failing that, ANY information pointing me in the right direction would be helpful, as I'm more than happy to fix it myself and submit a patch. If anyone else is finding this a problem, please reply in this thread. :-) I'm completely with you James. Moments ago I wrote this: http://www.fry-it.com/at/refresh-production-zopes which I think is a brilliant solution to updating product/live Zope instances without downtiming the server and losing SESSION variables for users on the site during the restart. Product refreshing is important for me for my future in Zope land. Because I depend on product refreshing so much it means I can't dip into Zope 2.9. Apparently the bug is somewhere deep in the ZODB code (thanks Dieter Maurer for pointing this out some time ago) and that's a domain I'm very very novice in debugging. Peter -- Peter Bengtsson, work www.fry-it.com home www.peterbe.com hobby www.issuetrackerproduct.com ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: ZEO Problem Clients Waiting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gerhard Schmidt wrote: HI, we have quite a Problem with out Zope/Zeo system. We run at the moment Zope cluster with 10 application servers and a zeo server with Filestorage. Our Data.fs is 3.5 Gig at the moment (after Pack). I runs most of the time without problem. But sometimes things screw up 2006-08-07T14:29:19 INFO ZEO.StorageServer (97002/10.152.64.23:52518) Transaction +blocked waiting for storage. Clients waiting: 1. 2006-08-07T14:29:29 INFO ZEO.StorageServer (97002/10.152.64.18:60205) Transaction +blocked waiting for storage. Clients waiting: 2. 2006-08-07T14:29:39 INFO ZEO.StorageServer (97002/10.152.64.19:55021) Transaction +blocked waiting for storage. Clients waiting: 3. 2006-08-07T14:29:39 INFO ZEO.StorageServer (97002/10.152.64.15:62775) Transaction +blocked waiting for storage. Clients waiting: 4. 2006-08-07T14:29:41 INFO ZEO.StorageServer (97002/10.152.64.22:59407) Transaction +blocked waiting for storage. Clients waiting: 5. 2006-08-07T14:29:41 INFO ZEO.StorageServer (97002/10.152.64.20:51153) Transaction blocked waiting for storage. Clients waiting: 6. 2006-08-07T14:29:41 INFO ZEO.StorageServer (97002/10.152.64.21:52951) Transaction blocked waiting for storage. Clients waiting: 7. 2006-08-07T14:29:41 INFO ZEO.StorageServer (97002/10.152.64.14:53919) Transaction blocked waiting for storage. Clients waiting: 8. 2006-08-07T14:29:41 INFO ZEO.StorageServer (97002/10.152.64.17:54463) Transaction blocked waiting for storage. Clients waiting: 9. 2006-08-07T14:29:47 INFO ZEO.StorageServer (97002/10.152.64.16:53743) Blocked transaction restarted. Clients waiting: 8 2006-08-07T14:29:47 INFO ZEO.StorageServer (97002/10.152.64.23:52518) Blocked transaction restarted. Clients waiting: 7 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.23:52518) Transaction blocked waiting for storage. Clients waiting: 8. 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.18:60205) Blocked transaction restarted. Clients waiting: 7 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.19:55021) Blocked transaction restarted. Clients waiting: 6 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.15:62775) Blocked transaction restarted. Clients waiting: 5 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.22:59407) Blocked transaction restarted. Clients waiting: 4 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.20:51153) Blocked transaction restarted. Clients waiting: 3 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.21:52951) Blocked transaction restarted. Clients waiting: 2 2006-08-07T14:29:48 INFO ZEO.StorageServer (97002/10.152.64.16:53743) Transaction blocked waiting for storage. Clients waiting: 3. 2006-08-07T14:29:49 INFO ZEO.StorageServer (97002/10.152.64.14:53919) Blocked transaction restarted. Clients waiting: 2 2006-08-07T14:29:50 INFO ZEO.StorageServer (97002/10.152.64.17:54463) Blocked transaction restarted. Clients waiting: 1 2006-08-07T14:29:50 INFO ZEO.StorageServer (97002/10.152.64.23:52518) Blocked transaction restarted. This one was a very quick one only 30 seconds. I have Blocked Transaktion that ware waiting for more than 2 minutes. When there a 9 Clients waiting our complete Zopesite comes to a halt until the transaction is restarted. As im not realy deep in the ZODB/ZEO subject. Can anybody pinpoint me where to look for the Problem. I think I would re-post your message over on the zodb-dev list, where the folks hang out who actually know this stuff. ;) Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE10xW+gerLs4ltQ4RAv66AKCIs6HcYKfKolIb2w2CsxMmKVJVIgCgj6aM R6vNjxqSo7qtU8ckK9JfIIw= =uMzW -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Renamed user account and OpenFlow
Hello everyone, I'm currently taking over the administration of a running instance of Zope and OpenFlow. These have been used to create a workflow for a decision making process. The users are authenticated via LDAP. The problem is, one of the workflow users got married and the username has been changed to reflect the new last name. Instances already in the workflow are assigned to the old username, and the person cannot log in to interact with them. I can assign the new username to the correct role, but what about the old instances? Is there an easy way of migrating the instances assigned to the old username to the new one, or maybe creating a local user with the old username? Any step-by-step suggestion is welcome, as I'm barely getting familiar with the admin interface. Thanks in advance, Titel ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Renamed user account and OpenFlow
This is mostly an OpenFlow question, so you would better post it to openflow mailing list. The simplest way would be creating a python script which: 1) search the old (inactive) workitem; 2) unassign them 3) reassign them Regards Marco On 8/7/06, Tit-Liviu Leontin [EMAIL PROTECTED] wrote: Hello everyone, I'm currently taking over the administration of a running instance of Zope and OpenFlow. These have been used to create a workflow for a decision making process. The users are authenticated via LDAP. The problem is, one of the workflow users got married and the username has been changed to reflect the new last name. Instances already in the workflow are assigned to the old username, and the person cannot log in to interact with them. I can assign the new username to the correct role, but what about the old instances? Is there an easy way of migrating the instances assigned to the old username to the new one, or maybe creating a local user with the old username? Any step-by-step suggestion is welcome, as I'm barely getting familiar with the admin interface. Thanks in advance, Titel ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) -- Marco Bizzarri http://notenotturne.blogspot.com/ ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
On 8/7/06, James Davies [EMAIL PROTECTED] wrote: Hi. I've been attempting to develop products with Zope 2.9, and am finding it increasingly difficult and slow to do so as Product refreshing no longer works. Google shows up a few results from mailing lists with somewhat negative responses (The gist I'm getting is that no-one 'in the know' wants to worry about fixing it, as they don't see a real need for it). Yeah, too bad, but making it better is complicated, and it can never be perfect anyway. Another major issue I've discovered is Zope hosting. We reguarly deploy custom sites on shared zope environments, and having to restart an entire server just to update one product severely breaks our uptime guarentee. You mean you can't allow the server even to be down for the less than a minute it takes to restart it? I would honestly be very interested in knowing what kind of systems you run that has that sort of requirements. But in any case, as mentioned by others here, multiple ZEO-clients and load balancing fixes this for most cases. I'm hoping I can garner some support to get the zope developers to fix the problem. Well, I'm sure it can be improved by throwing money on the right people... ;) -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] FastCGI server crashing
I am experiencing seemingly random crashes of the Zope FastCgi server that are really annoying users. Any help most appreciated. Apache errors: FastCGI: comm with server /space/apache2/fcgi-bin/zope.cgi aborted: idle timeout (30 sec) FastCGI: incomplete headers (0 bytes) received from server /space/apache2/fcgi-bin/zope.cgi Zope error: 2006-08-07T11:17:36 ERROR(200) ZServer uncaptured python exception, closing channel ZServer.FCGIServer.FCGIChannel connected 127.0.0.1:43792 at 0x43c13e2c (socket.error:(32, 'Broken pipe') [/usr/local/python235/lib/python2.3/asynchat.py|initiate_send|218] [/usr/local/python235/lib/python2.3/asyncore.py|send|337]) System: Redhat 7.3 Apache 2.0.52 mod_fastcgi 2.4.4 Python 2.3.5 Zope 2.7.8 Thanks! ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: FastCGI server crashing
Looks like the problem was an inbound RSS feed from a server that was down. The FastCGI process was timing out before the RSS request from CMFSin timed out. David Chandek-Stark wrote: I am experiencing seemingly random crashes of the Zope FastCgi server that are really annoying users. Any help most appreciated. Apache errors: FastCGI: comm with server /space/apache2/fcgi-bin/zope.cgi aborted: idle timeout (30 sec) FastCGI: incomplete headers (0 bytes) received from server /space/apache2/fcgi-bin/zope.cgi Zope error: 2006-08-07T11:17:36 ERROR(200) ZServer uncaptured python exception, closing channel ZServer.FCGIServer.FCGIChannel connected 127.0.0.1:43792 at 0x43c13e2c (socket.error:(32, 'Broken pipe') [/usr/local/python235/lib/python2.3/asynchat.py|initiate_send|218] [/usr/local/python235/lib/python2.3/asyncore.py|send|337]) System: Redhat 7.3 Apache 2.0.52 mod_fastcgi 2.4.4 Python 2.3.5 Zope 2.7.8 Thanks! ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: FastCGI server crashing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7 Aug 2006, at 12:09, David Chandek-Stark wrote: Looks like the problem was an inbound RSS feed from a server that was down. The FastCGI process was timing out before the RSS request from CMFSin timed out. You're probably aware of the fact that FastCGI is no longer a supported configuration. Is there any specific reason you're using it instead of RewriteRules for example? jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE1210RAx5nvEhZLIRAieRAJ9Di9HdK4HWS+oAtIXLlW+A/KtsmQCgtJga lqpJCUmCmyMCceQe29H7vf0= =YLu4 -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: FastCGI server crashing
Jens Vagelpohl wrote: You're probably aware of the fact that FastCGI is no longer a supported configuration. Is there any specific reason you're using it instead of RewriteRules for example? jens Actually, I wasn't aware. I'm using FastCGI b/c I am doing external authentication with an Apache module that sets REMOTE_USER. I have to use FastCGI to pass this variable to Zope and am using RemoteUserFolder for the Zope authentication. I am hoping that I will be able to move to PAS with Shibboleth, but haven't had time ... Major app is a Plone 2.0.5 site. Thanks, David ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: FastCGI server crashing
- Original Message - From: David Chandek-Stark [EMAIL PROTECTED] To: zope@zope.org Sent: Monday, August 07, 2006 2:04 PM Subject: [Zope] Re: FastCGI server crashing Jens Vagelpohl wrote: You're probably aware of the fact that FastCGI is no longer a supported configuration. Is there any specific reason you're using it instead of RewriteRules for example? jens Actually, I wasn't aware. I'm using FastCGI b/c I am doing external authentication with an Apache module that sets REMOTE_USER. I have to use FastCGI to pass this variable to Zope and am using RemoteUserFolder for the Zope authentication. I am hoping that I will be able to move to PAS with Shibboleth, but haven't had time ... I haven't done this myself, but according to the apache docs (http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html) the mod_rewrite module has access to REMOTE_USER and using url rewriting you should be able to pass it along (and thereby get rid of fastcgi). Jonathan ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
Andreas Jung wrote at 2006-8-7 13:56 +0200: ... Refreshing was always a hack and never something I would call a feature. It was always a hack for *development* purposes but not for production. We are speaking about development, not about production. ... Refresh does not work Five... Do you understand why? In my view, refreshing should work with Five. For this to work, we almost sure need to tell Five that the product was refreshed such that Five can reprocess the *.zcml files for the product. ... Another major issue I've discovered is Zope hosting. We reguarly deploy custom sites on shared zope environments, and having to restart an entire server just to update one product severely breaks our uptime guarentee. Refresh only works in debug-mode. You want to tell us that you are running a production site in debug-mode? I think you err, Andreas. Refresh always works, at least the explicit refresh (do not know about the automatic one which I have never used). ... I'm hoping I can garner some support to get the zope developers to fix the problem. I am a great fan of refresh and would try to get it fixed if we had a need for it. But, we decided recently, to stick with Zope 2.8.1 until Zope 2.11 is released. This means, it may take some time that I need to get active... Nevertheless, it may come sooner as some external developpers are a fan of Five and want to install a newer version. As we all expect Five to be the reason that refresh no longer works, this might force me to look into this problem earlier than I currently think. ... Dieter Maurer wrote a RefreshTool product lately (not sure if this would solve your problem and not sure if he released it). The refresh tool is employer's work and therefore not released. Furthermore, it solves a problem with dependent product refreshs but I am not sure whether it will solve the Five problem -- maybe, if it would be sufficient to refresh Five as well. @James: you may try this: refresh your product, then refresh Five. If this succeeds, then a technique similar to the RefreshTool may be sufficient. -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: Zope 2.9 Refreshing
Peter Bengtsson wrote at 2006-8-7 15:14 +0100: ... Apparently the bug is somewhere deep in the ZODB code (thanks Dieter Maurer for pointing this out some time ago) and that's a domain I'm very very novice in debugging. You must have misinterpreted me: I can assure you that the ZODB is not responsible for the product refresh breakage. I cannot tell you what it responsible (as we do not yet use Zope 2.9) but I am almost convinced that Five is to blame. I believe that the problem could be fixed -- but probably, Five has to change for this. -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
--On 7. August 2006 20:30:11 +0200 Dieter Maurer [EMAIL PROTECTED] wrote: Andreas Jung wrote at 2006-8-7 13:56 +0200: ... Refreshing was always a hack and never something I would call a feature. It was always a hack for *development* purposes but not for production. We are speaking about development, not about production. We're also talking about techniques to avoid downtime. So we are are also speaking of production :-) ... Refresh does not work Five... Do you understand why? No, and I did not try. In my view, refreshing should work with Five. For this to work, we almost sure need to tell Five that the product was refreshed such that Five can reprocess the *.zcml files for the product. I think this is basically a Zope 3 issue and not a Zope 2 issue. There were also some approaches in Z3 to make browser views somehow refreshable but I nothing that appeared in a release so far. ... Another major issue I've discovered is Zope hosting. We reguarly deploy custom sites on shared zope environments, and having to restart an entire server just to update one product severely breaks our uptime guarentee. Refresh only works in debug-mode. You want to tell us that you are running a production site in debug-mode? I think you err, Andreas. See my later posting. Refresh always works, at least the explicit refresh (do not know about the automatic one which I have never used). ... I'm hoping I can garner some support to get the zope developers to fix the problem. I am a great fan of refresh and would try to get it fixed if we had a need for it. Nevertheless, it may come sooner as some external developpers are a fan of Five and want to install a newer version. As we all expect Five to be the reason that refresh no longer works, this might force me to look into this problem earlier than I currently think. This is basically an issue when you work with Plone. Loading the complete boilerplate really takes ages. An instance running on a decent machine will start fast when you work with CMF friends. -aj pgpB8eS8trvf1.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
James Davies wrote at 2006-8-7 21:47 +1000: I've been attempting to develop products with Zope 2.9, and am finding it increasingly difficult and slow to do so as Product refreshing no longer works. What happens when you try to refresh a product? Does it happen only when the product uses Five? Or can even products not using Five not be refreshed? -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
Reinoud van Leeuwen wrote at 2006-8-7 14:15 +0200: On Mon, Aug 07, 2006 at 10:12:42PM +1000, James Davies wrote: We have Zeo, but running a seperate instance of zope for each site is still too much (We probably host around 50 sites at the moment, and growing. The only economical way to do this is to put multiple sites in one zope instance). Still you can shutdown 1 ZEO client; update products there and start it up again... There will be some performance degradation but the sites stay up... You need to restart all ZEO clients such that they see the new product all. Furthermore, your session data must be stored persistently for this to work (which is considerably less efficient that storing them in RAM). -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] ZEO Problem Clients Waiting
Gerhard Schmidt wrote at 2006-8-7 15:54 +0200: ... 2006-08-07T14:29:19 INFO ZEO.StorageServer (97002/10.152.64.23:52518) Transaction +blocked waiting for storage. Clients waiting: 1. ... 2006-08-07T14:29:50 INFO ZEO.StorageServer (97002/10.152.64.17:54463) Blocked transaction restarted. Clients waiting: 1 2006-08-07T14:29:50 INFO ZEO.StorageServer (97002/10.152.64.23:52518) Blocked transaction restarted. This one was a very quick one only 30 seconds. I have Blocked Transaktion that ware waiting for more than 2 minutes. This means that you have very long transactions -- transactions that take very long to commit. ZEO cannot commit two transactions for the same storage at the same time. Therefore, it sets a storage look when a transaction commit begins for the storage. If another transaction tries to commit to the same storage, the transaction is blocked until the first transaction commit completes. That's your Transaction blocked waiting for storage When the commit is completed, then a waiting transaction is restarted. That's your Blocked transaction restarted. You should try to understand where the huge transactions come from. Very often, they are caused by poor persistency design (either far too huge objects or an immense number of tine objects or just some stupidity (e.g. writing objects unnecessary). -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] FastCGI server crashing
David Chandek-Stark wrote at 2006-8-7 11:37 -0400: I am experiencing seemingly random crashes of the Zope FastCgi server that are really annoying users. Any help most appreciated. Apache errors: FastCGI: comm with server /space/apache2/fcgi-bin/zope.cgi aborted: idle timeout (30 sec) FastCGI: incomplete headers (0 bytes) received from server /space/apache2/fcgi-bin/zope.cgi Zope error: 2006-08-07T11:17:36 ERROR(200) ZServer uncaptured python exception, closing channel ZServer.FCGIServer.FCGIChannel connected 127.0.0.1:43792 at 0x43c13e2c (socket.error:(32, 'Broken pipe') [/usr/local/python235/lib/python2.3/asynchat.py|initiate_send|218] [/usr/local/python235/lib/python2.3/asyncore.py|send|337]) What you see is almost surely a long running request: Apparently your Apache is configured that a 30s timeout is in effect for the FastCGI communication. After the timeout, Apache abort the request. When Zope finally completes, it tries to send the response and fails because the connection was closed by Apache (that's the ZServer uncaptured python exception). You may try to increase the timeout -- or avoid long running requests ... -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] EMERGENCY!
How do I undo the last change I made in Zope from the server itself? I send Zope into an infinite loop when I call Web sites! beno ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
Andreas Jung wrote at 2006-8-7 20:43 +0200: ... Nevertheless, it may come sooner as some external developpers are a fan of Five and want to install a newer version. As we all expect Five to be the reason that refresh no longer works, this might force me to look into this problem earlier than I currently think. This is basically an issue when you work with Plone. Loading the complete boilerplate really takes ages. An instance running on a decent machine will start fast when you work with CMF friends. We know that already AT (and CMF) cause slow startup. Probably, Plone will make it worse but even without it, we want something comparable to refresh. -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
Aloha, Refresh always works, at least the explicit refresh (do not know about the automatic one which I have never used). I'm on 2.7 and yes, the explicit and *very* useful refresh tab in the ZMI seems to work fine in production mode also. I do not remember fondly the old days (2.4, 2.5) of having to restart zope for every little product change/tweak/debug effort during development, or when doing a minor product upgrade to production server. I was going to upgrade to 2.9 very soon but now may go only to 2.8. I don't have the technical chops to work on a refresh solution in 2.9+, however I heartily support such efforts from those of you who also see it as an important issue. cheers, John S. -- John Schinnerer - MA, Whole Systems Design -- - Eco-Living - Whole Systems Design Services People - Place - Learning - Integration [EMAIL PROTECTED] http://eco-living.net ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
The real effort towards making a better refresh should likely be spent at the level of the Python interpreter. The dynamic nature of Python is the thing that allows for a refresh in the first place, but the implementation of Python object references limits its usefulness. The implementation of reload could be vastly improved by changing Python internally to allow for a sort of mark-and-sweep reload that could traverse an object graph full of references between an object and the modules that it is declared in. Anything else will likely be too fragile to work in all cases. On Aug 7, 2006, at 4:36 PM, John Schinnerer wrote: Aloha, Refresh always works, at least the explicit refresh (do not know about the automatic one which I have never used). I'm on 2.7 and yes, the explicit and *very* useful refresh tab in the ZMI seems to work fine in production mode also. I do not remember fondly the old days (2.4, 2.5) of having to restart zope for every little product change/tweak/debug effort during development, or when doing a minor product upgrade to production server. I was going to upgrade to 2.9 very soon but now may go only to 2.8. I don't have the technical chops to work on a refresh solution in 2.9+, however I heartily support such efforts from those of you who also see it as an important issue. cheers, John S. -- John Schinnerer - MA, Whole Systems Design -- - Eco-Living - Whole Systems Design Services People - Place - Learning - Integration [EMAIL PROTECTED] http://eco-living.net ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: FastCGI server crashing
- Original Message - From: David Chandek-Stark [EMAIL PROTECTED] To: Jonathan [EMAIL PROTECTED] Sent: Monday, August 07, 2006 2:53 PM Subject: Re: [Zope] Re: FastCGI server crashing I haven't done this myself, but according to the apache docs (http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html) the mod_rewrite module has access to REMOTE_USER and using url rewriting you should be able to pass it along (and thereby get rid of fastcgi). No, you can't pass authorization headers with a proxy rule. You may want to have a look at this thread: http://mail.zope.org/pipermail/zope3-users/2005-November/001460.html Jonathan ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
Since I never knew the refresh tab was a fragile hack, it always worked fine for me... :-) Are you saying that a really good solution for this is in the hands of python developers, not zope developers? In that case it seems far off, if ever, since zope is only one of many many applications using python. I would settle for another fragile hack that works, I guess. The volume of posts so far would seem to indicate that it's not a trivial topic... John S. Chris McDonough wrote: The real effort towards making a better refresh should likely be spent at the level of the Python interpreter. The dynamic nature of Python is the thing that allows for a refresh in the first place, but the implementation of Python object references limits its usefulness. The implementation of reload could be vastly improved by changing Python internally to allow for a sort of mark-and-sweep reload that could traverse an object graph full of references between an object and the modules that it is declared in. Anything else will likely be too fragile to work in all cases. On Aug 7, 2006, at 4:36 PM, John Schinnerer wrote: Aloha, Refresh always works, at least the explicit refresh (do not know about the automatic one which I have never used). I'm on 2.7 and yes, the explicit and *very* useful refresh tab in the ZMI seems to work fine in production mode also. I do not remember fondly the old days (2.4, 2.5) of having to restart zope for every little product change/tweak/debug effort during development, or when doing a minor product upgrade to production server. I was going to upgrade to 2.9 very soon but now may go only to 2.8. I don't have the technical chops to work on a refresh solution in 2.9+, however I heartily support such efforts from those of you who also see it as an important issue. cheers, John S. -- John Schinnerer - MA, Whole Systems Design -- - Eco-Living - Whole Systems Design Services People - Place - Learning - Integration [EMAIL PROTECTED] http://eco-living.net ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) -- John Schinnerer - MA, Whole Systems Design -- - Eco-Living - Whole Systems Design Services People - Place - Learning - Integration [EMAIL PROTECTED] http://eco-living.net ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
On Aug 7, 2006, at 5:57 PM, John Schinnerer wrote: Since I never knew the refresh tab was a fragile hack, it always worked fine for me... :-) Bliss! I'm happy for you! FWIW, you've just had it nail you now, whereas I'd had it nail me four years ago, and swore it off then. ;-) Are you saying that a really good solution for this is in the hands of python developers, not zope developers? Yes. In that case it seems far off, if ever, since zope is only one of many many applications using python. There are many non-Zope applications that could benefit from better reload support in Python including any application that could benefit from running continuously without restart. Improving Python this way is a rising tide floats all boats sort of thing, maybe worthy of some sort of sprint at PyCon or something like it. I would settle for another fragile hack that works, I guess. The volume of posts so far would seem to indicate that it's not a trivial topic... Honestly I have no idea how trivial or nontrivial fixing the current Refresh implementation is, and frankly (shame on me, yes, I'm selfish, I'm sorry) I don't care. It doesn't hurt me because I don't develop using all of Plone often, so my startup times are reasonably acceptable. Even if I did develop using all of Plone often, I'd likely try to find the root causes of the slow startup and fix them or fix Python rather than fixing the Zope Rrefresh implementation. I realize that by having that position, I'm likely in the minority as a consumer, but unfortunately for those consumers, my position is likely shared by the majority of producers (core developers). ;-) - C ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
This isn't really a solution. Clients will still lose session data, which is unacceptable. -James. On Monday 07 August 2006 22:15, Reinoud van Leeuwen wrote: On Mon, Aug 07, 2006 at 10:12:42PM +1000, James Davies wrote: We have Zeo, but running a seperate instance of zope for each site is still too much (We probably host around 50 sites at the moment, and growing. The only economical way to do this is to put multiple sites in one zope instance). Still you can shutdown 1 ZEO client; update products there and start it up again... There will be some performance degradation but the sites stay up... (and I hope you've got enough ZEO clients so that bringing 1 down will not cause severe problems...) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
On Tuesday 08 August 2006 01:34, you wrote: You mean you can't allow the server even to be down for the less than a minute it takes to restart it? I would honestly be very interested in knowing what kind of systems you run that has that sort of requirements. Are you serious? People pay large sums of money for us to host there critical business infrastructure. If we have to restart zope for any reason, people get apache proxy errors and lose session data. -James. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Question of ZPL etiquette
Hi. I am trying to get a better sense of how others are dealing with ZPL headers in code from original authors once changes are made. For example if a package is ZPL copyright somebody, I typically see a header at the top of most files as well as the LICENSE.txt in the package itself. When changes are made however, it is typical see headers replaced with the header of the author(s) who have made changes and date. A second license will now apply to the modified package with the ZPL license of the original code left to acknowledge authors and copyright of the original product/package. Is that a fair assessment? Is that generally acceptable? Many thanks. Regards, David ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Question of ZPL etiquette
--On 8. August 2006 00:53:09 -0300 David Pratt [EMAIL PROTECTED] wrote: Hi. I am trying to get a better sense of how others are dealing with ZPL headers in code from original authors once changes are made. For example if a package is ZPL copyright somebody, I typically see a header at the top of most files as well as the LICENSE.txt in the package itself. When changes are made however, it is typical see headers replaced with the header of the author(s) who have made changes and date. A second license will now apply to the modified package with the ZPL license of the original code left to acknowledge authors and copyright of the original product/package. Is that a fair assessment? Is that generally acceptable? Many thanks. The ZPL does not tell what to put into header of your files. My source basically contains a reference to some LICENSE file in the root directoy. This file contains the main license (e.g. ZPL) but it also mentions all code parts that are published under a different license. So you have everything in one place and you don't have to modify all headers as soon as something changes with your licenses. -aj pgpS6u9fUxG0X.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
