Scott Spence wrote:
> But according to Ted's posting his config.db had the nobody:mailman
> permission - not the mailman:mailman permission - so when the cron is run
> the permissions will change from nobody:mailman to mailman:mailman
> (rw-rw----) right?
My crontask runs as mailman.mailman, however the webserver runs as httpd.daemon.
Whenever something comes through over the web, config.db becomes httpd.mailman,
however as
soon as the next crontask runs, everything becomes mailman.mailman again.
All the files ought to be owned by mailman.mailman, and the sticky bit should help
in
retaining the permissions even after the web server has changed.
--
W | I haven't lost my mind; it's backed up on tape somewhere.
+--------------------------------------------------------------------
Ashley M. Kirchner <mailto:[EMAIL PROTECTED]> . 303.442.6410 x130
IT Director / SysAdmin / WebSmith . 800.441.3873 x130
Photo Craft Laboratories, Inc. . 3550 Arapahoe Ave. #6
http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.
------------------------------------------------------
Mailman-Users maillist - [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
