Re: [cobalt-users] Need correct permissions for /usr/local/majordomo on RaQ3

[Jeff Lasman <jblists@xxxxxxxxxxxxx>]

At 11:18 AM 3/16/00 +0100, you wrote:

> On installing some additional components, this damned install script
> screwed up all my permissions and ownerships in the /usr/local
> directory. Now all owenerships are set to root, but the more severe
> problem is the change in permissions, because majordomo ceased to
> work:
>
>    wrapper: Trying to exec /usr/local/majordomo/resend failed:
>    Permission denied

Since you don't tell us what package(s) you installed, I can't help you there.

> Now, reenabling read and execute permissions for the wrapper and
> resend component doesn´t solve the problem:
>
>    Configuration file "/usr/local/majordomo/majordomo.cf" is not
>    owned by effective UID.
>
> Thus, can anyone please provide me with the correct settings for
> the /usr/local/majordomo directory on a RaQ 3. As a suggestion,
> you might execute
>
>    ls -l /usr/local/majordomo > majordomoinfo.txt
>
> and forwarding the majordomoinfo.txt file to me (you might want
> to delete the lines concerning subdirectories for specific
> lists/sites before forwarding the file - unless you want me to
> know which domains you are hosting).

Nothing in this directory listing that tells you anything about my system 
or sites, so I don't mind posting it here.

Note that I've got a RaQ2; as far as I can tell, I've NEVER made any 
changes to this copy of Majordomo; it should be as installed by 
Cobalt.  But I can't guarantee that; I might have made some changes I don't 
remember.

Anyway, this seems to work for the lists on the RaQ2.  I never use it for 
lists I host; they run on a different copy of majordomo installed at 
/usr/local/majord.

Here it is:

> [root admin]# ls -l /usr/local/majordomo
> total 268
> drwxr-xr-x   2 admin    daemon       1024 Nov 16 19:13 Tools
> -rwxr-xr-x   1 admin    daemon       5234 Mar 11  1999 archive2.pl
> drwxrwxr-x   2 admin    daemon       1024 Dec 15 13:51 archives
> drwxr-xr-x   2 admin    daemon       1024 Nov 16 19:13 bin
> -rwxr-xr-x   1 admin    daemon       2795 Mar 11  1999 bounce-remind
> -rwxr-xr-x   1 admin    daemon      10671 Mar 11  1999 config-test
> -rwxr-xr-x   1 admin    daemon      49738 Mar 11  1999 config_parse.pl
> -rwxr-xr-x   1 admin    daemon      13031 Mar 11  1999 digest
> drwxrwxr-x   2 admin    daemon       1024 Dec 17 01:15 digests
> drwxrwxr-x   3 admin    daemon       3072 Mar 14 22:20 lists
> -rw-rw-rw-   1 admin    daemon       5550 Dec 17 00:17 log
> -rwxr-xr-x   1 root     root        64253 Dec 16 12:16 majordomo
> -rw-r--r--   1 admin    daemon      10571 Dec 14 14:16 majordomo.cf
> -rwxr-xr-x   1 root     root        23763 Mar 11  1999 majordomo.pl
> -rwxr-xr-x   1 admin    daemon        137 Mar 11  1999 majordomo_version.pl
> -rw-r--r--   1 admin    daemon       1050 Mar 11  1999 post-install
> -rwxr-xr-x   1 admin    daemon       3532 Mar 11  1999 request-answer
> -rwxr-xr-x   1 admin    daemon      29520 Mar 11  1999 resend
> -rw-r--r--   1 admin    daemon      10462 Mar 11  1999 sample.cf
> -rwxr-xr-x   1 admin    daemon       8060 Mar 11  1999 shlock.pl
> -rwsr-xr-x   1 admin    daemon      14033 Mar 11  1999 wrapper
> [root admin]#

And here's the copy of a hard-working system I've installed at 
/usr/local/majord:

> [root admin]# ls -l /usr/local/majord
> total 328
> drwxr-xr-x   2 majordom daemon       1024 Dec 16 15:14 Tools
> -rwxr-xr-x   1 majordom daemon       5234 Dec 16 15:14 archive2.pl
> drwxrwxr-x   6 majordom daemon       1024 Dec 28 15:45 archives
> drwxr-xr-x   2 majordom daemon       1024 Dec 16 15:13 bin
> -rwxr-xr-x   1 majordom daemon       2795 Dec 16 15:13 bounce-remind
> -rwxr-xr-x   1 majordom daemon      10671 Dec 16 15:14 config-test
> -rwxr-xr-x   1 majordom daemon      49673 Dec 16 15:13 config_parse.pl
> -rwxr-xr-x   1 majordom daemon      13031 Dec 16 15:14 digest
> drwxrwxr-x   4 majordom daemon       1024 Dec 26 21:23 digests
> -rwxr-xr-x   1 majordom daemon      12321 Dec 16 16:28 jwd
> drwxrwxr-x   2 majordom daemon       2048 Mar 16 08:05 lists
> -rw-rw-r--   1 majordom daemon      54507 Mar 16 07:18 log
> -rwxr-xr-x   1 majordom daemon      64240 Dec 22 13:12 majordomo
> -rw-r--r--   1 majordom daemon      10796 Dec 26 10:39 majordomo.cf
> -rwxr-xr-x   1 majordom daemon      23763 Dec 16 15:13 majordomo.pl
> -rwxr-xr-x   1 majordom daemon        137 Dec 16 15:13 majordomo_version.pl
> lrwxrwxrwx   1 root     daemon          7 Dec 17 01:09 majordwrapper -> 
> wrapper
> drwxr-xr-x   4 majordom daemon       1024 Dec 16 15:14 man
> -rwxr-xr-x   1 majordom daemon       3532 Dec 16 15:13 request-answer
> -rwxr-xr-x   1 majordom daemon      29520 Dec 16 15:13 resend
> -rw-r--r--   1 majordom daemon      10462 Dec 16 15:14 sample.cf
> -rwxr-xr-x   1 majordom daemon       8060 Dec 16 15:13 shlock.pl
> -rwsr-xr-x   1 root     daemon      12321 Dec 22 08:56 wrapper
> [root admin]#

Explaining how to set up such a second copy of majordomo, and especially 
why I've got majordwrapper -> wrapper, is well beyond the scope of this post.

Just take it from me, after a lot of work, it does work, and works well.

Jeff

--
Jeff Lasman <jblists@xxxxxxxxxxxxx>