On Sunday 25 February 2001 09:24, R.I.P. Deaddog wrote:
> You've complained this many times, and seems nobody bothers to answer.
> The reason is you either played with msec or used highest security during
> installation.
> chkconfig will fail then, preventing unconscious adjustment in services
> starting/stopping.
>
> lowering the security level with msec (e.g. "msec 3") and everything will
> work again.
I haven't played with msec and chose security level 4, the level Mandrake
recommends in its documentation for servers.
I agree that with level 4, NEW services should be disabled - that's what's
defined in the comments in /usr/share/msec/custom.sh and that's what I expect.
I disagree that existing services should be turned off by a freshen. I would
have hoped that the user settings would be retained. After all, you wouldn't
expect any other setting to be reset to a pre-defined default either would
you? Would you be happy if Konqueror decided to change your home page on a
freshen?
To check the current settings on an existing service is trivial
# chkconfig $SERVICE --list
If it's on when you start the freshen, it should be left on when you finish,
no matter what the security settings. This is not an "unconscious
adjustment" - I simply want to leave things the they were before the upgrade.
My security level is set to a recommended level for servers (level 4). I
have not done any extra customizations other than to turn services on or off.
This should not mean that I should never upgrade my packages. Even a
"mandatory" security upgrade for an existing package will disable the
service, hardly something I would expect Mandrake to enforce on users.
That said, you have pointed me in the right direction and it looks like if I
manually keep /etc/security/msec/server.4 up to date whenever I turn a
service on or off, rpm -F seems to perform as expected.
--
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED]
