http://bugzilla.novell.com/show_bug.cgi?id=549915 http://bugzilla.novell.com/show_bug.cgi?id=549915#c1 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |bnc-team-screening@forge.pr |ovo.novell.com |ovo.novell.com --- Comment #1 from Jeff Mahoney 2009-12-02 21:55:35 UTC --- nfsserver might be special since it creates a kernel thread that holds a file system reference. Shutting down all services at shutdown probably isn't desired since it just makes it take longer for services that aren't even running. At any rate, this was misfiled as a kernel issue. Kicking it back to Basesystem. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=549915 http://bugzilla.novell.com/show_bug.cgi?id=549915#c2 Ruediger Oertel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #2 from Ruediger Oertel 2010-05-17 15:08:08 UTC --- I think it's possible to produce many such constructs: manually starting processes that keep things open (possibly with the help of the kernel). I'd propose to keep it simple and say: if someone manually started a server he should also manually stop it as well. I'd say that "insserv /etc/init.d/nfsserver" is probably even quicker than editing boot.local ... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.