Bug 2027 - xinit should handle SIGTERM similar to SIGINT
Summary: xinit should handle SIGTERM similar to SIGINT
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: App/xinit (show other bugs)
Version: 6.7.0
Hardware: All Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-07 02:41 UTC by Andreas Luik
Modified: 2011-10-15 16:37 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
xinit.c: handle SIGTERM (similar to SIGQUIT etc.) (993 bytes, patch)
2004-12-07 02:48 UTC, Andreas Luik 		no flags Details | Splinter Review
View All

Description Andreas Luik 2004-12-07 02:41:29 UTC 
xinit properly handles SIGINT, as well as SIGQUIT and SIGHUP.
Unfortunately, it does not handle SIGTERM, but it should.
Reason: I use xinit in /etc/inittab to automatically start an
X Server in run-level 4.  This works fine.  If I switch to
run-level 3 (telinit 3), init sends SIGTERM to xinit.  xinit
terminates, but does not kill the X Server (or any clients it
started).  So right now, the X server continues to run in level 3.
The correct behaviour would be xinit to catch SIGTERM, and shutdown
the X Server and clients.
Comment 1 Andreas Luik 2004-12-07 02:48:48 UTC 
Created attachment 1487 [details] [review]
xinit.c: handle SIGTERM (similar to SIGQUIT etc.)

I do not see a reason why handling SIGTERM would result in any problems.
Comments?
Comment 2 Adam Jackson 2005-10-03 18:27:39 UTC 
applied to head, thanks!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.