Re: [PATCH] rfkill: allow user to exit gracefully from event watching loop

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 8 November 2017 at 11:31, Karel Zak <kzak@xxxxxxxxxx> wrote:
> On Tue, Nov 07, 2017 at 04:08:56PM +0000, Sami Kerola wrote:
>> When SIGINT is raised by something else than an user running rfkill the
>> watch loop will be killed by that signal with appropriate exit code.
>
> It seems like over-engineering that introduces unnecessary code and
> complex semantic. Why do you care about return code when you press
> CTRL+C and why it should be different to another situations with
> signals? I think we do not have such code in another utils.

My thinking is distincting inbetween user oneself vs someone / something
else sent signal is worth knowing. This sort of user exit or killed could be
done in other tools as well, but I reading the reply I don't think distinction
is seen interesting enough. Lets call this as rejected proposal and be
done with this.

-- 
Sami Kerola
http://www.iki.fi/kerolasa/
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux