[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220519122746.GA3904@localhost>
Date: Thu, 19 May 2022 14:27:46 +0200
From: Pavel Machek <pavel@....cz>
To: Arseny Maslennikov <ar@...msu.ru>
Cc: Walt Drummond <walt@...mmond.us>, Theodore Ts'o <tytso@....edu>,
"Eric W. Biederman" <ebiederm@...ssion.com>, aacraid@...rosemi.com,
viro@...iv.linux.org.uk, anna.schumaker@...app.com, arnd@...db.de,
bsegall@...gle.com, bp@...en8.de, chuck.lever@...cle.com,
bristot@...hat.com, dave.hansen@...ux.intel.com,
dwmw2@...radead.org, dietmar.eggemann@....com, dinguyen@...nel.org,
geert@...ux-m68k.org, gregkh@...uxfoundation.org, hpa@...or.com,
idryomov@...il.com, mingo@...hat.com, yzaikin@...gle.com,
ink@...assic.park.msu.ru, jejb@...ux.ibm.com, jmorris@...ei.org,
bfields@...ldses.org, jlayton@...nel.org, jirislaby@...nel.org,
john.johansen@...onical.com, juri.lelli@...hat.com,
keescook@...omium.org, mcgrof@...nel.org,
martin.petersen@...cle.com, mattst88@...il.com, mgorman@...e.de,
oleg@...hat.com, pbonzini@...hat.com, peterz@...radead.org,
rth@...ddle.net, richard@....at, serge@...lyn.com,
rostedt@...dmis.org, tglx@...utronix.de,
trond.myklebust@...merspace.com, vincent.guittot@...aro.org,
x86@...nel.org, linux-kernel@...r.kernel.org,
ceph-devel@...r.kernel.org, kvm@...r.kernel.org,
linux-alpha@...r.kernel.org, linux-arch@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-m68k@...r.kernel.org,
linux-mtd@...ts.infradead.org, linux-nfs@...r.kernel.org,
linux-scsi@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: Re: [RFC PATCH 0/8] signals: Support more than 64 signals
Hi!
> > The only standard tools that support SIGINFO are sleep, dd and ping,
> > (and kill, for obvious reasons) so it's not like there's a vast hole
> > in the tooling or something, nor is there a large legacy software base
> > just waiting for SIGINFO to appear. So while I very much enjoyed
> > figuring out how to make SIGINFO work ...
>
> As far as I recall, GNU make on *BSD does support SIGINFO (Not a
> standard tool, but obviously an established one).
>
> The developers of strace have expressed interest in SIGINFO support
> to print tracer status messages (unfortunately, not on a public list).
> Computational software can use this instead of stderr progress spam, if
> run in an interactive fashion on a terminal, as it frequently is. There
> is a user base, it's just not very vocal on kernel lists. :)
And often it would be useful if cp supported this. Yes, this
is feature I'd like to see.
BR, Pavel
--
Powered by blists - more mailing lists