[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Need correct permissions for /usr/local/majordomo on RaQ3
- Subject: RE: [cobalt-users] Need correct permissions for /usr/local/majordomo on RaQ3
- From: "Oliver Hasprich" <Oliver.Hasprich@xxxxxx>
- Date: Thu Mar 16 13:23:34 2000
> From: cobalt-users-admin@xxxxxxxxxxxxxxx
> [mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Jeff Lasman
>
> > 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.
To be exact, I´ve installed the OpenLink ODBC drivers package. I
started the installation script in the /usr/local directory as
there was no mention in the installtion guides etc. on which
location to use. This was a mistake because the script didn´t
create a new subdirectory to extract the archive´s content into it.
Instead, it used the current directory for installation purposes
and changed the file owner/group settings not only for the installed
files but for all existing files in this hierarchy.
Well, after all I got it up and running and was able to make
ODBC connections to a MS-SQL Server via PHP3 pages. :)
> 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.
As you´ve installed your own copy of majordomo, you know that
majordomo usually is installed under its own user account. You did
it this way and if I´m installing it on a common Linux-PC, i create
a separate majordomo user, too. But I found no 'majordom' user in
the RaQ´s passwd file, thus Cobalt must have majordomo running under
a different user. And I didn´t know which one.
Althoug your directory listing didn´t solved my problem, it lead
me to the solution. I have changed all ownership settings to
mail.daemon and this made it work again.
BTW: Is there a reason why you´ve set up a separate majordomo
installation to host mailing lists?
BTW2: I don´t really use majordomo for mailing lists, but I
have a few clients who want their info@... aliases to be
directed on more than one user account. So I set up a mailing
list with that alias and include all site users in this list.
At least that seems to be the easiest way for me to make it
work and the client can configure the settings himself via
the web interface. If you have an even better solution, I´d
be grateful to hear it.
> Just take it from me, after a lot of work, it does work, and works well.
<smile> I´ve made some majordomo installations for myself, thus
I know about the hassles it takes to get it up and running.
Thanks for your help!
Oliver Hasprich