Prana <[EMAIL PROTECTED]> writes:
[...]
> Just wanna let you know that there's this bug since v7.1 and not fixed
> yet until 8.0 Beta 1. Mandrake 7.2 doesn't provide any fix for this
> either. If I update an RPM package (with MandrakeUpdate or just urpmi)
> that has /etc/rc.d/init.d entry that I _Have_ turned OFF, why does it
> ***always forces me to turn on the services again*** ???
Okay, after talking with fred, we came with a solution to this problem.
Actually, the current way of doing the things is okay: when you do a
chkconfig --level 345 httpd off, it only modifies the local states of the
sysv links in the initscripts for each runlevel.
The information on whether a service should be started is not kept as
links; the links are just the way the system is used. The information is
kept after a special token named "chkconfig:" in the header of the
initscript.
If you modify this rather than modifying with chkconfig --level, the
upgrade should be smooth and keep your config.
I'm currently working on a patch to chkconfig, so that chkconfig --level
will modify the header of the initscript accordingly.
--
Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
