>> Darn! why do I have to be the exception!? My UID/GID are exactly the
>> same in the makefile as defined in etc/passwd, yet majordomo requests
>> crunch almost forever. And finally end with the imfamous "Out of
>> Memory" error message. I have read the FAQ at least four times &
>> can find no reason that Perl 4.036/Majordomo V1.93 would behave
>> this way. I'm sure that it's a dumb error on my part, but cannot
>> *FIND* it...??
>> johnd
>
>The problem is that when sendmail runs majordomo, it is running under the
>UID and GID which are defined in your sendmail.cf file. Look for the Og# for
>GID, and Ou# for UID.
>
>My wrapper is not SUID nor GUID, but all my majordomo files are group
>writable by the same group that sendmail runs under and things work fine.
Perhaps it's my newbieness, but I do not understand. It is true
that my sendmail runs under a different GID & UID than majordomo, but
1) my wrapper does run SUID/GUID to the majordomo IDs. This seems to
be what the FAQ recommends for POSIX. ?
2) all majordomo files (except wrapper) are readable/writable by other
groups. Would this not mean that the sendmail group could read/write
the majordomo files? Would it help to add sendmail to the majordomo
group in the etc/group file?
My clue meter seems to be reading zero at the moment.....
real confused,
johnd
Follow-Ups:
|
|
