[Bug 623460] New: rcxdm restart doesn't wait for stop before issuing start
http://bugzilla.novell.com/show_bug.cgi?id=623460 http://bugzilla.novell.com/show_bug.cgi?id=623460#c0 Summary: rcxdm restart doesn't wait for stop before issuing start Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs@forge.provo.novell.com ReportedBy: jnelson-suse@jamponi.net QAContact: xorg-maintainer-bugs@forge.provo.novell.com CC: mt@novell.com, werner@novell.com Depends on: 622058 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #622058 +++ the xdm init script suffers from the same issue discovered in Bug 622058. Can a fix for the xdm script also be supplied? Actually, this seems like it might be a more systemic issue. Why was the change made in the first place? It seems like this issue might effect many packages. -- 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=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c1
Stefan Dirsch
Why was the change made in the first place?
Which change? -- 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=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c2
Jon Nelson
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c3
--- Comment #3 from Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c4
--- Comment #4 from Jon Nelson
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c5
Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c6
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c7
Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c8
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c9
--- Comment #9 from Jon Nelson
Normally the package should not depend on the old behaviour that is that 5 seconds should be enough to terminate a normal server daemon.
And yes I've look through out the services. Currently only cups is known to have a problem for restart.
The question is *why* SIGTERM takes that long for xdm od gdm or xdm or any other display manager? And why was this problem discoverd that late as the changes was done at Mon Apr 12 17:49:46 CEST 2010.
Compare with bug #595796 and bug #622058
With all due respect, I believe that there still exists an issue with lots of packages. A quick "grep TERM /etc/init.d/* | grep killproc" shows 36 of 110 init scripts (on this machine) make use of killproc -TERM in some way. I recently discovered that haldaemon is *also* susceptible to this particular issue. To me, the core issue is the fact that many init scripts are specifying the -TERM which means that with the new killproc behavior they do not wait _at all_. I would wager that a great many of the init scripts which currently specify -TERM would not reliably restart their packages if the system were under any sort of load or the program took more than a fraction of a second to exit. -- 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=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c10
--- Comment #10 from Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c11
Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c12
Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c13
--- Comment #13 from Marcus Meissner
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c14
--- Comment #14 from Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c15
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c16
Christian Dengler
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c
Stefan Dirsch
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c17
Dr. Werner Fink
http://bugzilla.novell.com/show_bug.cgi?id=623460
http://bugzilla.novell.com/show_bug.cgi?id=623460#c
Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com