- Zope - Zope lists

Zope as daemon, shows up with owner as root
by Robert Oschler 24 Aug '02

24 Aug '02

I have Zope starting as a daemon, still inhibits further boot log messages after it starts, but it is starting. I notice that in the process list (KDE's kpm utility), it shows up as 'python' with the owner being 'root'. All the other zope processes show up with the owner being 'nobody'. Is this correct? Or will the launch script showing up as owned by 'root' create a security problem. thx

2 1

encoding URLs in Python Scripts?
by Andreas Kostyrka 24 Aug '02

24 Aug '02

Hi! I've been wondering how to urlencode a string in a Python Script. Andreas

2 1

storing images
by 3205 5361 1215 9784 24 Aug '02

24 Aug '02

Hello zope, i want to store images, and call them by id. it needs to be used from other places, so it will go in a mysql table, base64 encoded. how to write a function, that gets the image by id, and returns it to the browser with the correct content type? i should use a python script for that? or can it be made in dtml or pt? how to make it respond to this? http://zopehost/images/image_id.jpg or something similar? ... with 'images' being the script.... thanks, k -- don't believe everything you think

2 1

Re: [Zope] Compile Zope with Python v2.2.1 instead of v2.1.3
by Wayne 24 Aug '02

24 Aug '02

rising to the occasion. Thanks all for your help. Andreas Kostyrka wrote: > > Am Fre, 2002-08-23 um 02.44 schrieb Wayne: > > I have set up Zope on a freebsd machine with > > Zope 2.5.1_1 > > FreeBSD 4 > > Python 2.1.3 > > ZMySQL 2.0.8 > > > > My problem is that ZMySQL requires a Zope with version > > of Python 2.2.1 to work. > Well, if ZMySQL requires Python 2.2.1, which I doubt, > then you've got a > package for a future Zope *grin* > > Andreas

1 0

Compile Zope with Python v2.2.1 instead of v2.1.3
by Wayne 24 Aug '02

24 Aug '02

I have set up Zope on a freebsd machine with Zope 2.5.1_1 FreeBSD 4 Python 2.1.3 ZMySQL 2.0.8 My problem is that ZMySQL requires a Zope with version of Python 2.2.1 to work. How do i compile Zope with this version of Python. Currently Zope package installs with Python 2.1.3 as default. Thanks in advance. Wayne

3 2

RE: [Zope] Vhosting
by sean.upton＠uniontrib.com 24 Aug '02

24 Aug '02

How 'bout a slightly different approach: Setup Squid on port 80; use a redirector. Search freshmeat for pyredir; it's a good one, written in python, and very simple to use. The redirector is your friend, and makes virtual hosting work quite nicely; it acts like Apache's mod_rewrite, and plays well witha Virtual Host Monster. Instructions assume you use Zope with a VHM, and perhaps (might) want SSL and load-balancing for ZEO. Setup requirements: Squid, Zope, use of a VHM, use of a redirector, and optionally OpenSSL if you want SSL accel. Details: 1 - Prerequisites: OpenSSL; realpath and stat commands; Chris McDonough's squidctl script (find on the squid-users mailing list); pyredir 2 - Go download Squid 2.5pre10 source; untar in a directory of your choice. 3 - ./configure --prefix=/usr/local/squid --enable-dlmalloc --enable-pthreads --enable-storio=aufs --with-openssl=/usr/lib/include/openssl --disable-internal-dns --disable-identd-lookups --enable-ssl --> This is for Linux; you may want to adjust --enable-pthreads and use of aufs, since I think you want to use diskd instead on BSD --> Change path to openssl include files 4 - make && make install --> Squid will install in /usr/local/squid ($PREVIX) --> Squid.conf will be in /usr/local/squid/etc --> Sometime between Squid 2.5pre5 and Squid2.5pre10, the dir layout switched so that the squid binary is in $PREFIX/sbin 5 - Put the pyredir script in $PREFIX/libexec 6 - Put the pyredir.conf file in $PREFIX/etc 7 - Edit/hack pyredir: --> Disable redirector logging in the code if you have a big server (perhaps later, after this works?) --> Change path to log and pyredir.conf file --> Make sure all needed commands are supported (GET,POST,HEAD,etc) 8 - Put a VHM in the folder(s) you want to act as your host. 9 - Edit pyredir.conf: #this rule is for the public url mysite1.foo.com, which should #be accessed via SSL on port 443 on Squid... #it says ^http:// becuase squid passes the URL to the redirector #with the https stripped off so it is more like a normal URL. #note: there is a Zope VHM in the MySite1 folder ^http://mysite1.foo.com[/]?(.*) =http://zopeserver:8080/MySite1/VirtualHostBase/https/mysite1.foo.com:443/My Site1/VirtualHostRoot/\1 #Note that this one is http (not https) in the rewrite rule passed eventually to the virtual host monster ^http://mysite2.foo.com[/]?(.*) =http://zopeserver:8080/MySite2/VirtualHostBase/http/mysite2.foo.com:443/MyS ite2/VirtualHostRoot/\1 10 - Add "zopeserver" to /etc/hosts --> if you have a ZEO cluster, add the name zopeserver for every IP in your cluster; it will be round-robined --> Squid uses dnsserver (a resolver helper child program) for /etc/hosts support since its internal resolver only works with DNS --> this is why we compiled with --disable-internal-dns 11 - Set up any ssl keys/certs you need with openssl. 12 - Setup squid: http_port 80 #You will need to setup these keys with openssl first: https_port 443 cert=/usr/local/squid/var/mysite1.foo.com_cert.pem key=/usr/local/squid/var/mysite1.foo.com_key.pem cache_dns_program /usr/local/squid/libexec/dnsserver dns_children 5 redirect_program /usr/local/squid/libexec/pyredir redirect_children 12 redirect_rewrites_host_header off httpd_accel_host virtual httpd_accel_port 80 httpd_accel_single_host off httpd_accel_uses_host_header on #obviously there are other things to set up, these #are the interesting/specific ones 13 - Download and setup the squidctl script in /usr/local/squid --> you will have to change the path to reflect that the squid binary is in $PREFIX/sbin --> hack/adjust as necessary 14 - Chreate the cache dir; make sure permissions are okay for nobody/nogroup. --> Start squid; pay attention to any warnings about misconfig, and fix 15 - Adjust: --> ACLs in squid.conf as needed. --> Pyredir rules in pyredir.conf 'killall -s HUP pyredir' will reload rules without a squid restart --> SSL config, if needed 16 - Once squid is going, make sure DNS or hosts on your client points to your accelerator box, and try the URL... 17 - Once you have everything working, if you have a ZEO cluster, give consideration to trying the ICP patches for Zope to allow for true load-balancing by adding Zope servers to Squid's notion of its caching fabric... 18 - Email me with questions if anything doesn't work. I plan on trying to turn these really rough notes into a howto at some point on Zope.org, but I'm too busy at the moment. Perhaps discussion here on the list will help me with that process. Questions, thoughts? Sean -----Original Message----- From: Adam Getchell [mailto:AdamG@hrrm.ucdavis.edu] Sent: Friday, August 23, 2002 3:51 PM To: 'Charlie Reiman'; Marc Lindahl; Quentin Smith; Adam Getchell Cc: zope(a)zope.org Subject: RE: [Zope] Vhosting Hello all, Okay, so I read the links you gave me. http://www.zope.org/Documentation/Books/ZopeBook/2_6Edition/VirtualHosting.s tx http://www.zope.org/Members/Jace/apache-vhm http://www.zope.org/Members/bowerymarc/squid-zserver-virtual Starting from scratch, I created a zope user on my OpenBSD box, with a home directory of /home/zope. I then ran # /usr/local/bin/zope-instance /home/zope as root, to create an instance of Zope. # chmod -R zope:nobody /home/zope # su zope # /home/zope/start & To start Zope as user zope. I then logged into the site, created my /site1 and /site2 folders, and created a Virtual Host monster with mappings of: site1.ucdavis.edu/site1 site2.ucdavis.edu/site2 At this point, going to site1.ucdavis.edu goes to the main website, while going to site1.ucdavis.edu:8080 goes to the subfolder. So I think my Squid configuration is off. I went through /etc/squid/squid.conf and have the following options enabled (not commented out): http_port 80 acl QUERY urlpath_regex cgi-bin \? no_cache deny QUERY cache_dir diskd /var/squid/cache 100 16 256 emulate_httpd_log on auth_param basic children 5 auth_param basic real Squid proxy-caching web server auth_param basic credentialsttl 2 hours httpd_accel_host my.ip. httpd_accel_port 8080 httpd_accel_single_host on I'm confused about the ACL's in step 4 of http://www.zope.org/Members/bowerymarc/squid-zserver-virtual I don't see an acl of type webserver in squid.conf ... So what should that line be? acl ext-ip-addr site1.ucdavis.edu www.xxx.yyy.zzz/255.255.255.255 And then the ACL is ...? Http_access allow MATCH ext-ip-addr Clearly, the zope side of things are working so far. What is the SiteAccessEnhanced used for? Do I still need a site root in each virtual folder? Many thanks, --Adam -----Original Message----- From: Charlie Reiman [mailto:creiman@kefta.com] Sent: Friday, August 23, 2002 9:06 AM To: Marc Lindahl; Quentin Smith; Adam Getchell Cc: zope(a)zope.org Subject: RE: [Zope] Vhosting You should also read the 2.6 docs on VHM. They're downright tasty. http://www.zope.org/Documentation/Books/ZopeBook/2_6Edition/VirtualHosting.s tx They apply to 2.5.1 as far as I noticed. > -----Original Message----- > From: zope-admin(a)zope.org [mailto:zope-admin@zope.org]On Behalf Of > Marc Lindahl > Sent: Thursday, August 22, 2002 11:42 PM > To: Quentin Smith; Adam Getchell > Cc: 'zope(a)zope.org' > Subject: Re: [Zope] Vhosting > > > Try: http://www.zope.org/Members/bowerymarc/squid-zserver-virtual > > > on 8/22/02 10:15 PM, Quentin Smith at quentins(a)comclub.dyndns.org > scrivened: > > > Hi- > > Use a Virtual Host Monster, one in the root of the site. Ideally, you > > should put Apache or Pound in front of Zope instead of squid, but you > > can use the Mappings tab of the Virtual Host Monster to define the > > virtual hosts. I used to use SiteRoots for my site, and none of the > > directions I found actually worked. > > HTH, > > --Quentin > > On Thursday, August 22, 2002, at 08:27 PM, Adam Getchell wrote: > > > >> Hello all, > >> > >> I've read and re-read > >> http://www.zope.org/Members/4am/SiteAccess2/vhosting a > >> number of times. > >> > >> I have a webserver that needs to host a bunch of different sites, > >> site1.ucdavis.edu, site2.ucdavis.edu, etc. > >> > >> I planned to use name based redirection, so I have c-names to the IP > >> address > >> of the server, i.e. site1.ucdavis.edu --> IP, site2.ucdavis.edu --> IP, > >> etc. > >> > >> I installed on OpenBSD, so Zope runs as an instance in /home/zoperoot > >> under > >> port 8080, and Squid sits in front of it and redirects from 80 to port > >> 8080. > >> This part is working fine. > >> > >> Under my main zope site, I created two folders, site1 and site2. I then > >> created, in each folder, an empty SiteRoot. That is, Title, Base, and > >> Path > >> are all blank. At least, that's how I interpreted the directions above. > >> > >> I then created a DTML method called host_redirector, with the following > >> content: > >> > >> Extract the part of HTTP_HOST we care about, and declare our rewrite > >> dictionary. > >> <dtml-let hostname="_.string.upper(_.string.split(HTTP_HOST, '.')[0])" > >> sitemap="{'SITE1': 'site1', > >> 'SITE2': 'site2'}"> > >> Do we have a match? > >> <dtml-if expr="sitemap.has_key(hostname)"> > >> Set the logical root: <dtml-call "REQUEST.set('SiteRootPATH', '/')"> > >> Add physical root: <dtml-call > >> "REQUEST['TraversalRequestNameStack'].append(sitemap[hostname])"> > >> </dtml-if> > >> </dtml-let> > >> > >> Since I only care about the first part of the name, I rewrote > the script > >> from the example. It may be incorrect! I tried the equivalent at a > >> python > >> interpreter, but I may certainly have goofed up. > >> > >> In the root folder, I Set an Access rule to host_redirector. > >> > >> I changed the index pages in each of Site1 and Site2 to differentiate > >> them. > >> However, going to site1.ucdavis.edu gives the top level index_html, > >> while > >> going to site1.ucdavis.edu/site1 gives index_html in the Site1 folder, > >> so > >> clearly I did something wrong. > >> > >> Any pointers? > >> > >> *************************** > >> * Adam Getchell > >> AdamG(a)hrrm.ucdavis.edu > >> * System Architect/Programmer (530) 752-1584 > >> * Human Resources Information Systems > >> http://www.hr.ucdavis.edu/ > >> *************************** > >> "Invincibility is in oneself, vulnerability in the opponent." > -- Sun Tzu > >> > >> > >> > >> > >> _______________________________________________ > >> Zope maillist - Zope(a)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 ) > >> > > > > > > _______________________________________________ > > Zope maillist - Zope(a)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 ) > > > > > _______________________________________________ > Zope maillist - Zope(a)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 ) > _______________________________________________ Zope maillist - Zope(a)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 )

1 0

knowledge management with Zope
by Tim Wilson 23 Aug '02

23 Aug '02

Hi everyone, I just ran across a program called Scribe today. (http://chnm.gmu.edu/tools/scribe/index.html) This would seem to be the sort of thing that could work really well with Zope. Anyone tried anything like this? -Tim -- Tim Wilson | Visit Sibley online: | Check out: Henry Sibley HS | http://www.isd197.org | http://www.zope.com W. St. Paul, MN | | http://slashdot.org wilson(a)visi.com | <dtml-var pithy_quote> | http://linux.com

2 1

Getting Zope started as a daemon
by Robert Oschler 23 Aug '02

23 Aug '02

This is post is both a request for help and an FYI for those of you who are trying to get Zope started as a daemon on SuSE Linux 7.3 Pro: I'm running Linux SuSE 7.3 Pro. I'm trying to get the Zope server to start at boot-time. I found the 'jules' document on www.zope.org that gave steps to do so with 6.3, but after some modifications it still isn't working. As 'root' I followed the instructions given in the link http://www.zope.org/Members/jules/SuSE-6.3_html for setting up Zope as a daemon in Suse Linux. I made all the necessary adjustments for directory differences between 6.3 and 7.3 (e.g. - 'init.d' is a sub-dir off of '/etc' in 7.3 instead of being a sub-dir off of '/sbin' as it is in 6.3, according to 'jules' document). I changed the symbolic link files to be in rc5.d not rc2.d since SuSE 7.3 uses RUNLEVEL 5 not 2. I changed the number portions of the symbolic link files from the hard-coded '22' given in 'jules' document to '24' which was the next available daemon number. (If you look in rc5.d you'll see that all the 'K$' and 'S$' scripts are sequential. On my system '24' was the next available number). So I have 'K24zope' and 'S24zope' in my rc5.d directory. Lastly, if you make the 'START_ZOPE=yes' addition to rc.config, you still have to jump into 'yast2', and using the rc-config-editor module, change START_ZOPE to 'yes'. This will result in SuSEconfig running and setting things up properly. If you don't, then you will find out that even though the rc.config line is 'START_ZOPE=yes', if you print out the value of the command line argument to 'zope' ($1) you'll see that it is set to 'no'. After doing the 'yast2' operation it will be properly set to 'yes'. I then tested my sample script in an xterm window. Given the proper command line argument (start/stop/status), it started Zope successfully, stopped it, and gave a checkproc status all perfectly. When run at bootup however, after boot completes, if I look in the boot message log I see the 'zope' script startup messages, but none of the other messages from SuSE that used to follow the initialization of all daemon's. I think this is causing SuSE to kill the 'zope' process due to a timeout because when I get fully logged in, 'zope' is not in the kpm's process list at all. What's also strange is that I do have to run 'zope stop' to clear a lock-flag that 'lock_file.py' put in place, and then I can run 'zope start' again and it loads fine. Just to be very clear, it's the same behavior that occurs when you run 'zope start' from an xterm window. The script never returns until you shut down the zope server. I would suspect that this kind of behavior doesnt' sit well with the bootup scripts. So what do I have to do to have 'zope start' exit properly so it can run as a daemon? thx

1 0

Re: [Zope] Error: 'in ' requires character as left operand
by Dieter Maurer 23 Aug '02

23 Aug '02

Benjamin Eastwood writes: > thanks for your response! I'm still having the problem after undoing the > transaction, so I'm really confused now. worse than that, I then packed > the database, so no more undos... Oops. When you pack, the previous state is safed in a file called "Data.fs.old". Thus, you may go back. However, I expect that the new role was not your problem. I suspect a new product or a newly instantiated instance of a product to be causing the problem. Then the problem would not be in your ZODB but somewhere in the code base. Maybe, you catch the exception in "AccessControl/Role.py: 106" and print out the problem causing operands. This may give a hint where the problem lies. Dieter

2 2

RE: [Zope] Linux vs. UNIX vs. BSD
by sean.upton＠uniontrib.com 23 Aug '02

23 Aug '02

I'll second support for use of Debian. We use it in a lot of production tasks on a bunch of servers and for development workstations. That said, with some of our new boxes, we are using Debian, but compiling from source RedHat enterprise kernels (easier than patching stock kernel) to get better hardware monitoring, and more importantly, to get the O2 scheduler, which does have some crude CPU affinity support. I believe this is one area where Linux has been a bit behind some other Unix varieties. Though we haven't used it yet, as I understand it, CPU affinity is important to Python performance on SMP machines. I expect that we will write or find a simple user-space utility utilizing the new system calls to bind a group of processes to a single CPU. I think, in theory, this will allow us to successfully run two Zope instances on an inexpensive 2CPU machine, each instance bound to a respective CPU. Sean -----Original Message----- From: Mike Renfro [mailto:renfro@tntech.edu] Sent: Tuesday, August 20, 2002 8:19 AM To: Peter Bengtsson Cc: zope(a)zope.org Subject: Re: [Zope] Linux vs. UNIX vs. BSD On Tue, Aug 20, 2002 at 10:55:14AM +0100, Peter Bengtsson wrote: > For dev and desktop I personally prefer Mandrake, but what I like > becomes irrelevant when it's time to set up a serious server for > production use. I'm compelled to put in my two cents for Debian GNU/Linux now: - performance should be identical to any other Linux distribution on the same hardware. - configurability should also be identical, or exceeding other distributions. There's no overarching GUI configurator, but a combination between good policy on how packages are organized and tools never overriding your own settings without substantial warnings and chances to back out is nice. - not sure what you mean by "ease of use" and "lack of hacks". Most all common tasks (adding/deleting users, etc. ) already have scripts to handle them. Debian doesn't do much GUI integration, so this may count against your ease of use. On the other hand, I can administer a Debian server with a modem-enabled Palm. - RDBMS integration is there: packages already built for the usual Unix SQL servers. - Backup should be comparable to any other Unix. There's tar, dump, cpio, and afio for low-level tools (don't just use cat /dev/hdwhatever, please). There's tob, taper, afbackup, amanda and others for high-level tools. You can of course always pay for BRU, Veritas, or whatever normally runs on Linux. - ZEO should be a non-issue, as well. If you can get it running anywhere, you shouldn't have any extra difficulties. Downsides include the historically slow release cycle (Zope went from 2.1.6 to 2.5.1 during the last Debian stable release), which can be somewhat mitigated by building your own packages, or doing what lots of people do: building it from source in /usr/local. One could always install something other than the "stable" release of Debian on a server, but I'd not recommend it for the inexperienced (it'll be similar to running some other Linux distribution's normal releases). Debian's stable releases are very, very stable, and if your server hardware is supported, they're about trivially maintainable. -- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University -- renfro(a)tntech.edu _______________________________________________ Zope maillist - Zope(a)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 )

3 2