bill@biome.bio.ns.ca (Bill Silvert) writes:
# I also found that this didn't work, but creating a mode 777 directory
# called Logs and creating a mode 777 directory in Logs called .locks and
# creating a mode 666 file in Logs caled Log and editing majordomo.cf
# solved the problem. Whew. There must be an easier (and more secure)
# way.
I don't know what all the fuss is about. The log (singular; it's a
file, not a directory) is going to go in whatever file you've
specified with the "$log" setting in the majordomo.cf file.
$log should be a _file_, not a directory.
This file needs to be writable by whatever uid/gid "wrapper" is
setuid/setgid to, so that Majordomo can write to it.
The directory containing this file also needs to be writable by
whatever uid/gid "wrapper" is setuid/setgid to, so that Majordomo can
create a lock file for the log.
-Brent
--
Brent Chapman Great Circle Associates
Brent@GreatCircle.COM 1057 West Dana Street
+1 415 962 0841 Mountain View, CA 94041
|
|
