> Make sure the old list file has the proper ownership, since that's where
> it's getting the UID to change it to. (It's possible that an earlier
> botched run had set an improper UID on the list file.) Otherwise, you need
> to investigate just why it's trying to chown to daemon; if the wrapper was
> really installed correctly and all of the ownerships are proper, you
> wouldn't have this problem.
Aha! Jason, you RULE! The ownership on the old list file was INDEED the
problem but I didn't SEE it as a problem because it's always worked that
was with v1.92 of MajorDomo ! While I'm at it, can you (or someone) verify
for me that this is how the owner/group ownerships and the permissions
should look for each of the files for a given group?
-rw-rw-r-- 1 majordom daemon 5895 Oct 23 14:21 incolsa-l
-rw-rw-r-- 1 daemon majordom 12105 Oct 15 17:05 incolsa-l.config
-rw-rw---- 1 majordom majordom 1961 Oct 15 17:05 incolsa-l.info
-rw-rw---- 1 majordom majordom 5 Oct 15 17:05 incolsa-l.passwd
Thanks again!
--
Tom Metzger -> INCOLSA Unix System Administrator -> http://www.palni.edu/~tom
Help Stop Internet Spam! ---> http://www.vix.com/spam/
Don't Spread That Hoax! -->
http://crew.umich.edu/~chymes/Hoaxes/Think.html
Follow-Ups:
References:
|
|
