On Thursday 11 April 2002 04:24 pm, Frederic Lepied wrote:
> Brook Humphrey <[EMAIL PROTECTED]> writes:
> > On Thursday 11 April 2002 11:09 am, Frederic Lepied wrote:
> > > > Yes like I stated erlier msec completely changes all the permisions
> > > > on all of djb software which make it imposible for the software to
> > > > run. It is so bad that the only real solution is to uninstall and
> > > > reinstall it all. I can't remember specificly but at the tme of
> > > > mandrake 8.0 pure-ftpd had this same problem. It may however be fixed
> > > > by now as pure is included in contribs at least.
> > > >
> > > > It whould be nice to have a working qmail setup after a clean
> > > > install. And at least in my case I don't really want to uninstall
> > > > msec as I enjoy the added secutity that it gives me.
> > >
> > > Sorry for the delay. First I must say that msec doesn't change the
> > > owner/group of subdirs of /var/log. If it'd do that it will have broken
> > > a lot of applicattions. It only changes the permissions and I
> > > understand that can be a problem if the group needs access to the
> > > subdir. Is it the case with qmail ?
> >
> > Remember qmail by default is in /var/qmail
> >
> > all it's binaries and everything operate out of there as per the license
> > that djb has for his software. I'm not sure I remember correctly as it
> > has been a long time since I tried to install it during the actual
> > install but Think that the permissions were incorrect in /var/log and
> > msec does do something to the /var/qmail directory also. I can't remember
> > if it was permissions only or if it changed user/group also for
> > /var/qmail.
>
> No msec doesn't change files/directories under /var, it only changes
> /var itself.
>
> That's very strange that msec breaks qmail as I remember Vincent has
> done tests and that was ok. Vincent ?
I was assuming msec was doing this but it may the installer itself. This only
occurs if I include qmail in my mandrake cd's and install it durring the os
install. If it is installed after the install is complete and the os is up
and running then this does not occur. So it may be the installer. Pixel may
know more about this. It may also be some script that runs during the first
boot after install. All I know is that it happens.
Thanks for the reply. Maybe we can get to the bottom of this werever it is.
--
-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-
Brook Humphrey
Mobile PC Medic, 420 1st, Cheney, WA 99004, 509-235-9107
http://www.webmedic.net, [EMAIL PROTECTED], [EMAIL PROTECTED]
Holiness unto the Lord
-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-
