Bugzilla – Bug 310539
some SuSE management application removes gpm from runlevel 5 w/o my implisit consent
Last modified: 2009-01-11 22:11:09 UTC
I'm tired to do do: ----------------- [ 13:46:53, root@sunbook, ~ ] # chkconfig -l gpm gpm 0:off 1:off 2:on 3:on 4:off 5:off 6:off ----------------- [ 13:47:00, root@sunbook, ~ ] # chkconfig gpm 2,3,5 ----------------- [ 13:47:29, root@sunbook, ~ ] # chkconfig -l gpm gpm 0:off 1:off 2:on 3:on 4:off 5:on 6:off ----------------- [ 13:47:31, root@sunbook, ~ ] # Some application I've not yet recognised touches the gpm presense in runlevels w/o my implicit consent. :/ Yes, I can use chattr +i on symlink, but it's definitely some brain damage in managing application - I periodically run, for example switching beetween network manager & traditional interface configuration due to another SuSE bug I've submitted on network manager. Also some times I install software & do other work w/ yast2. Any advises what kind of logging could be enabled to trace the problem to exact script/app?
*** This bug has been marked as a duplicate of bug 340646 ***
Unfortunate thing is that upgrading a package replaces /etc/init.d/PROGRAM, which means it gets new "Default-Start" and "Default-Stop" tags, and running insserv then updates the links in /etc/init.d/rc?.d according to these tags, effectively trashing your own, personal preferential, runlevel settings. This affects any service. Any idea how to reasonably give way for unoverridable personal settings?
Jan, this is a very interesting topic to discuss. Please, could you bring it to opensuse-packaging mailinglist? Thank you
Sent on August 11. Except that it was not replied to and probably forgotten already again.
Done in 11.1.