|
From: | Ognyan Kulev |
Subject: | Re: console-client signal handling |
Date: | Thu, 15 Jul 2004 13:29:40 +0300 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040413 Debian/1.6-5 |
Ognyan Kulev wrote:
Marco Gerards wrote:Many people complain on IRC about the console client and that it does not catch the signals. So when you send a SIGTERM signal to the console it does not correctly clean up its state. The same is true for the SIGINT signal.Why not add SIGQUIT too?
Or SIGHUP? I'm not sure what is correct.SIGQUIT is meant to terminate and dump core, so that core is inspected for errors. Perhaps we don't want to clean up drivers' state?
SIGHUP is for terminal hang-up, so we want to clean up state.Looking at the list of signals, these 4 seems to be the only user-controlled signals of interest.
Regards, ogi
[Prev in Thread] | Current Thread | [Next in Thread] |