--On Mittwoch, 19. Januar 2005 17:04 Uhr +1100 Alan Milligan
<[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
| There is zero need to relax this requirement. You only have to start
| Zope as root
I just explained you cannot start as root ...
And I expl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
| There is zero need to relax this requirement. You only have to start
| Zope as root
I just explained you cannot start as root ...
| to get port 80 but it is in general not a good idea for *any* service to
| run
| as root for securi
--On Mittwoch, 19. Januar 2005 15:18 Uhr +1100 Alan Milligan
<[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have a requirement to run a root uid Z2 process and was most surprised
to see that line 334 of Zope/Startup/__init__.py expressly forbids this,
throwing a Z
--On Dienstag, 18. Januar 2005 20:55 Uhr + Chris Withers
<[EMAIL PROTECTED]> wrote:
The next bug day is going to be on Thursday 27th November as an
experiment to see if those who complain about the Friday bug days can
make it. Hope to see all on #zope-dev next Thursday!
27th November
-aj
On Tuesday 18 January 2005 9:18 pm, Alan Milligan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> I have a requirement to run a root uid Z2 process and was most surprised
> to see that line 334 of Zope/Startup/__init__.py expressly forbids this,
> throwing a ZConfig.Configurati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have a requirement to run a root uid Z2 process and was most surprised
to see that line 334 of Zope/Startup/__init__.py expressly forbids this,
throwing a ZConfig.ConfigurationError
While it's not a good idea to configure Zope to run as root by de
Hi All,
It's a long time overdue, but here's the roundup. I suspect these all
made it into 2.7.4, if anyone's curious :-) The great news is that lots
of bugs were resolved, and it was especially good to see patches
contributed by people outside the usual core of developers. Thanks to
those peop
