Actually...... this is not a problem of chkconfig as stated before. This
is because of not enough checking before chkconfig...... true that the fix
below is a good enough temporary fix. Just dunno when a real fix will
follow though.
Abel Cheung
On Mon, 5 Mar 2001, Ed Wilts wrote:
> On Monday 05 March 2001 06:42, Eugenio Diaz wrote:
> > When you upgrade an rpm that contains a script with "chkconfig --add
> > servicename" you get a script filed message, when in fact nothing bad
> > happened, just that the service already existed and chkconfig returns a
> > status of 1.
>
> We had this discussion last week - I raised it. The problem is that
> Mandrake's version of chkconfig -add is broken at higher security levels (4
> or 5). If the service is not listed in /etc/security/msec/server.4 but the
> service is on, Mandrake's chkconfig -add will turn it off. This is a bug.
> What it should do is quietly return success and not do anything.
>
> I've been burned by this several times, getting services turned off that were
> running.
>
> The workaround, at least until chkconfig gets fixed, is to add the services
> manually to /etc/security/msec/server.4
