I added the user in the zope.conf file but this is what I get - is it because of the folder rights?
Traceback (most recent call last): File "/home/usr/zopeplone/lib/python/zdaemon/zdrun.py", line 719, in ? main() File "/home/usr/zopeplone/lib/python/zdaemon/zdrun.py", line 716, in main d.main(args) File "/home/usr/zopeplone/lib/python/zdaemon/zdrun.py", line 243, in main self.run() File "/home/usr/zopeplone/lib/python/zdaemon/zdrun.py", line 256, in run self.opensocket() File "/home/usr/zopeplone/lib/python/zdaemon/zdrun.py", line 278, in opensocke t sock.bind(tempname) File "<string>", line 1, in bind socket.error: (13, 'Permission denied') . . . . . . . . . . . . . . . . . . . . . . . . ^C > what david says is correct. > furthermore you must (as the error suggests) add the user as which the > zope process should run as to the zope config. > open the /yourInstance/etc/zope.conf in an editor and look for > "effective-user". > this you set to the name of the user as which you start zope. > > if you allways start zope as this user, the variable can be left unset. > however if you want to start zope as root > (eg in the start up process of your computer) then it MUST be set. > the reason for this is, that for security reason, zope is not allowed to > run as user root. > if started by user root, the zope.conf is consulted and the process > handed over to the effective user. > hence the need for this user to have rw permissions. > robert > > David H wrote: >> Ofer Weisglass wrote: >>> yes, it fixed the problem but now I have this error >>> it seems like user premission problem but I don't know how to solve it >>> >>> >>> /home/ofer/zope1/bin/runzope -X debug-mode=on >>> /home/usr/zopeplone/lib/python/ZServer/utils.py:33: DeprecationWarning: >>> The zLOG package is deprecated and will be removed in Zope 2.11. Use >>> the >>> Python logging module instead. >>> LOG('ZServer', severity[type], message) >>> 2006-07-09 00:16:23 INFO ZServer HTTP server started at Sun Jul 9 >>> 00:16:23 2006 >>> Hostname: 0.0.0.0 >>> Port: 8080 >>> 2006-07-09 00:16:23 CRITICAL Zope A user was not specified to setuid >>> to; >>> fix this to start as root (change the effective-user directive in >>> zope.conf) >>> Traceback (most recent call last): >>> File "/home/usr/zopeplone/lib/python/Zope2/Startup/run.py", line 56, >>> in ? >>> run() >>> File "/home/usr/zopeplone/lib/python/Zope2/Startup/run.py", line 21, >>> in run >>> starter.prepare() >>> File "/home/usr/zopeplone/lib/python/Zope2/Startup/__init__.py", line >>> 94, in prepare >>> self.dropPrivileges() >>> File "/home/usr/zopeplone/lib/python/Zope2/Startup/__init__.py", line >>> 213, in dropPrivileges >>> return dropPrivileges(self.cfg) >>> File "/home/usr/zopeplone/lib/python/Zope2/Startup/__init__.py", line >>> 382, in dropPrivileges >>> raise ZConfig.ConfigurationError(msg) >>> ZConfig.ConfigurationError: A user was not specified to setuid to; fix >>> this to start as root (change the effective-user directive in >>> zope.conf) >>> >>> >>> >>>> --On 24. Juni 2006 23:09:00 +0300 Ofer Weisglass <[EMAIL PROTECTED]> >>>> wrote: >>>> >>>> >>>>> Hi >>>>> >>>>> I am trying to install Zope 2.9.3 or 2.9.1 on Suse 10.1 and this is >>>>> what >>>>> I >>>>> get: >>>>> >>>>> error: must supply either home or prefix/exec-prefix -- not both >>>>> make: *** [install] Error 1 >>>>> >>>>> Any ideas what to do? >>>>> >>>>> >>>> Please try again with a Python source build. Usually we don't care >>>> much >>>> about system Python installation that are often broken in different >>>> ways. >>>> >>>> -aj >>>> >> Maybe this can help? >> >> This is from either Plope or Plone site (i think I snipped it long ago): >> << >> If you are running everything as root, you will get an instance that >> cannot be started, because a different effective user id is required >> for it to change to. Even if you create an account after the fact, >> that user cannot start zope because it doesn't have access to any of >> the instance files. >> >> The best way to run mkzopeinstance is to first su to another user (su >> zope) and then run mkzopeinstance.py. The zope user must have write >> access to create the directory. >> >> EFFECTIVE-USER >> After the instance is created, edit "effective-user zope" into the >> etc/zope.conf, so if you start it as root later it should su itself to >> the non-root user. >> >> >> >> 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 ) >> > > _______________________________________________ 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 )