Daniel> I've been reading the list, but I guess I must have missed it -- Daniel> what's the solution to the alpha-2 permissions problem that prevents Daniel> me from running zope as root/nobody so it can be on port 80?

(maybe this is it?) Make sure user nobody has read/write permissions on var/. What port(s) it listens on depends what options you pass z2.py

User nobody has read/write permissions on var. If I su - nobody, I can create and remove files there. It's a file creation problem, not a socket problem -- the same thing happens if I request port 9673 but run as root.

It seems pretty clear from this traceback that Zope does not have permissions to write a pid file. My guess is that since this bit of code operates after Zope has changed uid, nobody probably doesn't have write access to 'var/Z2.pid'

Make sure that the var directory *and all the files in it* are owned by the uid the Zope is running as.

$ chown -R nobody var $ chgrp -R nobody var

That doesn't work, even when I chmod 777 the directory and files. When I truss it, it seems to actually be complaining about not being able to write to stuff in /tmp (which is also writable by nobody/everybody).

On Tue, 15 Jun 1999 16:12:29 -0700, Amos Latteier <amos@aracnet.com> said: Amos> If you are having the same problem that Andrew Rice was earlier Amos> today with not being able to write to a select trigger file in the Amos> /tmp directory, I fixed this problem a couple hours ago, and the Amos> fix is in CVS. You need to update the Amos> ZServer/medusa/select_trigger.py file. Thanks Amos! Daniel, also if you don't want to CVS, this seems to work fine too: su -c 'python z2.py' nobody Alex