https://bugzilla.novell.com/show_bug.cgi?id=804454 https://bugzilla.novell.com/show_bug.cgi?id=804454#c12 --- Comment #12 from Thomas Fehr <fehr@suse.com> 2013-04-17 16:32:34 UTC ---
So, this poses the question again: - why is nscd running and who starts it? - should it not be automatically restarted anyways, because it was running during installation and thus it is likely that its configuration has changed?
I just did a test install if you enable nscd in <runlevel> section, it gets started by systemd before YaST2-Second-Stage gets started.
I think this is somewhat similar to the network service, which also is started and required during installation, but later needs to be restarted to adapt to its final configuration...
Network is the exception here. It probably would work to add "nscd.service" to the "Before" list of YaST2-Second-Stage.service but we can hardly add all existing services there. Another solution would be to add network.target to "After" section of nscd.service. I am not sure if it even makes any sense to start nscd before network is up, in pre-Systemd times it was dependent on $remote-fs and therefore indirectly on network. yast2-runlevel correctly does not start services. From the y2log: RunlevelEd.ycp:768 All services will be started at the end, skipping for now...
Are there any other service that are both required during installation and configured during installation? How is it handled there?
So far these services were expected not to be running while YaST2-Second-Stage is executed unless yast2 start scripts starts them (as an excpetion like for network). With 12.3 this is not true any more and will most probably lead to lots of subtle problems. Therefore I would urge to use final_reboot=true. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.