Great Circle Associates Majordomo-Users
(January 1996)

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Newbie question
From: Ford Prefect <fprefect @ friday . houston . net>
Date: Sun, 28 Jan 1996 18:27:28 -0600 (CST)
To: Ismail Ali <mael @ asiapac . net>
Cc: Chris Woods <cjwoods @ Paladin . COM>, "majordomo-users @ greatcircle . com" <majordomo-users @ GreatCircle . COM>
In-reply-to: <>

> > Sounds like a permissions problem. Be sure that ~majordom (assuming you
> > made the username `majordom') is 755 majordom.majordom, same for all
> > subdirectories. Be sure everything in those directories is UID/GID
> > majordom.majordom, all executable scripts are 755, all non-executable data
> > files (.cf, list names and config files, etc) are either 644 or 664, once
> > again, owned majordom.majordom. The *ONLY* exception is that the wrapper
> > binary is owned by root, and setuid (i.e. 4755). 
> Even though we didn't install majordomo files in ~majordom ? Yeah, what if
> we install majordomo in somewgere else, such /usr/local/pkg/majordomo1.93

Regardless, you still need to set the directories and files with 
permissions as detailed above, and make sure they're UID/GID majordom.

I personally use /tools/majordomo-1.93.  All I did was make sure this was 
the "home" directory for the "majordom" user.

Indexed By Date Previous: Re: Newbie question
From: Ismail Ali <>
Next: Re: resend.* files piling up
From: Clint Davis <>
Indexed By Thread Previous: Re: Newbie question
From: Ismail Ali <>
Next: RE: Newbie question
From: (Kevin Taylor)

Search Internet Search