Ognyan Kulev <[EMAIL PROTECTED]> writes: > 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.
Well, I could do that. Normally (on modern systems) it is used to restart the program. But in case of the console we should either ignore, reinitialize the console or exit it. I prefer it works alike the other signals and it will exit the console client. I will add that functionality. > 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? Right. Like I said in my other email, I prefer not to handle SIGQUIT. > SIGHUP is for terminal hang-up, so we want to clean up state. Right. > Looking at the list of signals, these 4 seems to be the only > user-controlled signals of interest. Great. Thanks for checking this. The book I have here did not cover SIGHUP so I `forgot' about it. Thanks, Marco _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-hurd
