[Zope] Unusual 2.7 runzope fail message!

Bob Bernstein rs at bernstein.providence.ri.us
Tue Apr 27 23:17:38 EDT 2004


Without apparent incident I have built Zope2.7 from the tarball,
using Python 2.3.3 (threaded) on this fairly current NetBSD
system. I create an instance under /usr/local and in etc/zope.conf
set an 'effective user', one that I've used for months now with my
Zope2.6 installation on this machine. Here's the output:

trollboy /usr/local/zope27 # bin/runzope &
[1] 1904
trollboy /usr/local/zope27 # ------
2004-04-27T01:49:15 INFO(0) ZServer HTTP server started at Tue Apr 27 01:49:15 2004
        Hostname: trollboy.host_obfuscated.org
        Port: 8088
Traceback (most recent call last):
  File "/usr/local/lib/Zope2.7/lib/python/Zope/Startup/run.py", line 49, in ?
    run()
  File "/usr/local/lib/Zope2.7/lib/python/Zope/Startup/run.py", line 19, in run
    start_zope(opts.configroot)
  File "/usr/local/lib/Zope2.7/lib/python/Zope/Startup/__init__.py", line 48, in start_zope
    starter.dropPrivileges()
  File "/usr/local/lib/Zope2.7/lib/python/Zope/Startup/__init__.py", line 203, in dropPrivileges
    return dropPrivileges(self.cfg)
  File "/usr/local/lib/Zope2.7/lib/python/Zope/Startup/__init__.py", line 347, in dropPrivileges
    initgroups.initgroups(effective_user, gid)
AttributeError: 'module' object has no attribute 'initgroups'

nb: 

If I build and run Zope2.7 entirely under an ordinary user's
$HOME account on this NetBSD system, the thing launches and runs
with no complaints at all! 

And, I don't see the errant behaviour on an OpenBSD 3.5 system in
my possession, using a similarly hand-rolled-from-tarball Zope2.7.

Does this ring a bell with anyone??


-- 
Bob Bernstein

   "A modern philosopher who has never once suspected himself of
    being a charlatan must be such a shallow mind that his work is
    probably not worth reading."        Leszek Kolakowski




More information about the Zope mailing list