linux-kernel - Re: [RFC] The SIGINFO signal from BSD

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <545A7B00.1040309@gmail.com>
Date:	Wed, 05 Nov 2014 14:31:12 -0500
From:	Austin S Hemmelgarn <ahferroin7@...il.com>
To:	Martin Tournoij <martin@...242.net>, linux-kernel@...r.kernel.org
Subject: Re: [RFC] The SIGINFO signal from BSD

On 2014-11-05 10:17, Martin Tournoij wrote:
> Hi there,
>
> As a long-time BSD user, I have become quite used to the SIGINFO (sent with ^t)
> feature; after switching to Linux as my desktop a few months ago, I very much
> miss this.
>
> SIGINFO prints the status of the process to the terminal; BSD cp, for example,
> shows show much data it's copied:
>
>      $ cp large_file /dev/null
>      <press ^t>
>      load: 1.39  cmd: cp 85837 [running] 3.91r 0.00u 0.98s 8% 2340k
>      large_file -> /dev/null  15%
>
> As you see, it shows the current load, pid, process status, memory usage, as
> well as how much of the file has been copied. Many other BSD tools print similar
> statistics (mv, tar, dd, sleep, fetch, etc.).
>
> On Linux, sometimes SIGUSR1 is used for similar purposes, the problem with this
> is that SIGUSR{1,2} will terminate a program if a program doesn't have a signal
> handler installed(!)
> SIGUSR1 also has no defined meaning, and may do something radically different;
> nginx, for example, reopens the logfiles on SIGUSR1, and SIGUSR2 upgrades the
> nginx executable on-the-fly.
>
> So you need to carefully inspect the documentation, hope it's not out of date,
> and then send SIGUSR1 and pray.
>
> This is different from SIGINFO, which does nothing when it's not installed,
> which is safe. You can send SIGINFO to any process, and not be afraid you kill
> it.
>
> In addition, it's also not easy to send SIGUSR1, you need to open a new
> terminal, find the pid, and use a kill command (you could also use
> pkill/killall, with the risk of sending the signal to other processes).
>
> SIGINFO is, AFAIK, supported since 4.4BSD & descendants (ie. all modern BSD
> systems), as well as MacOS X. Perhaps other systems as well (but did not
> investigate).
>
> Why don't we have SIGINFO on Linux? Would a patch to implement this be accepted?
>
> SIGINFO is not defined in any standard, but Linux already implements other
> useful non-standard signals (most notably SIGWINCH). IMHO it's a very useful
> feature.
>
> Thanks,
> Martin
>
> PS.
> I am *not* subscribed to this maillist; please cc me in replies!
Given a quick look at the signal(7) man page, it appears that on at 
least alpha and sparc systems, SIGINFO is a synonym for SIGPWR, which 
comes from SVR4, where it was used to indicate that the system had lost 
power (I don't really understand this usage, but my guess was that UPS 
monitoring software was supposed to send init a SIGPWR when the UPS 
switched off AC to the backup power source).

You have to understand however, that the reason that SIGINFO works like 
that on *BSD is that the kernel and core userspace are developed 
together, whereas on Linux, they are maintained entirely separately. 
Outside of core userspace components, using SIGINFO that way on *BSD is 
just convention.  The people to talk to about that for the core 
utilities on Linux would be the maintainers of the GNU coreutils, or 
whatever your distribution might use in their place (I think it's very 
unlikely that busybox or toybox would implement it however).



Download attachment "smime.p7s" of type "application/pkcs7-signature" (2455 bytes)