Hi Lisa,
Yes, I have read the install file and made sure I had all the points covered you
mentioned below a few days ago.
I finally just got it to work with help from gw and the "list".!! (thank you) I
believe the problem was the permissions and ownership on the wrapper. They are
now set to "wrapper 4755 root daemon". Probably since the sticky bit or the root
ownership was wrong, it wasn't able to do it's job.
Are you still having a problem with yours?
Thanks
~~~Jim
Liza Deatrick Peak wrote:
> Jim - these instructions were passed on to me and may help you.
>
> The list directory is owned by majordom.daemon (user.group).
> The problem you're running into seems pretty clearly covered by points one
> and three in the INSTALL file:
> 1) Pick a group and user ID for Majordomo to run under. Usually this
> is "majordomo.daemon".
> ( snip )
> 3) Edit the Makefile, defining where Perl and the C compiler are, the
> Majordomo home directory (chosen in step 2), the location of the
> manual pages, the user and group that Majordomo will run under, and
> the permissions for the various files and directories.
> In the Makefile, there are lines of the following form:
> # You need to have or create a user and group which majordomo will run as.
> # Enter the numeric UID and GID (not their names!) here:
> W_USER = 20
> W_GROUP = 2
> On my particular system, UID 20 = majordomo and GID 2 = daemon.
> This needs to be changed to reflect the values for majordomo and daemon
> on your system, then recompile and re-install.
> This question and the directory permissions problem are both covered in either
> the INSTALL or Doc/FAQ files in the distribution. Take the time to read these
> through before reinstalling. This isn't all that difficult, but the error
> messages put out by sendmail can be a bit cryptic sometimes.
>
> Hope this helps you -
> Liza
>
> At 10:22 AM 6/28/00 -0700, you wrote:
> >Liza,
> >
> >Well, in my case... the uid and gid in my error refers to the same uid and
> >gid that is running my httpd. Thanks for bringing that to my attention.
> >
> >Jim
> >
> >Liza Deatrick Peak wrote:
> >
> > > James I am also having similar problems my error message reads:
> > >
> > > JMAJORDOMO ABORT (mj_resend)!!
> > >
> > > shlock:'usr/local/majordomo-1.94.5/lists' is not writable by UID 8 GID 12
> > >
> > > I have check these ids and in both cases it is 'mail' - where/why is
> > > majordomo trying to uses this? Do your ids which your error message referr
> > > to 'mail'? I too have spent more time than I care to share trying to get
> > > this to work.
> > >
> > > Liza
> > >
> > > At 04:44 PM 6/27/00 -0700, you wrote:
> > > >Hello,
> > > >
> > > >Been working on this for more time than I would like to admit and
> > > >gotten my errors messages down to just one when I run: echo 'lists' |
> > > >mail majordomo
> > > >This is the E-mail I get. I've checked and rechecked all permissions
> > > >and ownership of file and directories. And tried several different
> > > >combinations.
> > > >
> > > >Has anyone had experience with problems with effective uid and gid. I
> > > >really appreciate any help anyone can give me. I'm using 777 majordom
> > > >majordom for the log file.
> > > >Thanks very much,
> > > >Jim
> > > >
> > > >
> > > >MAJORDOMO ABORT (mj_majordomo)!!
> > > >
> > > >While running with an effective uid of 65534 and an effective gid of
> > > >65534 65534, Majordomo
> > > >ran into the following problems:
> > > >Unable to write to log file, check permissions on
> > > >/usr/local/majordomo/Log
|
|
