Date: Wed, 29 Jun 2011 09:39:56 +0000 (UTC) From: Vadim Goncharov <vadim_nuclight@mail.ru> To: freebsd-bugs@freebsd.org Subject: Re: bin/155034: [PATCH] dd(1) dies on SIGUSR1; should print info Message-ID: <slrnj0lsnb.vuq.vadim_nuclight@kernblitz.nuclight.avtf.net> References: <201106061820.p56IKoDT040550@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi jh@FreeBSD.org! On Mon, 6 Jun 2011 18:20:50 GMT; jh@FreeBSD.org wrote about 'Re: bin/155034: [PATCH] dd(1) dies on SIGUSR1; should print info': > Synopsis: [PATCH] dd(1) dies on SIGUSR1; should print info > State-Changed-From-To: open->closed > State-Changed-By: jh > State-Changed-When: Mon Jun 6 18:04:17 UTC 2011 > State-Changed-Why: > Not a bug. As far as I can see ignoring the signal would violate POSIX: > "For SIGINT, the dd utility shall interrupt its current processing, > write status information to standard error, and exit as though > terminated by SIGINT. It shall take the standard action for all other > signals; - -" The originator requested compatibilty shim with Linux dd, in fact: info dd: Sending an `INFO' signal to a running `dd' process makes it print I/O statistics to standard error and then resume copying. [...] On systems lacking the `INFO' signal `dd' responds to the `USR1' signal instead, unless the `POSIXLY_CORRECT' environment variable is set. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?slrnj0lsnb.vuq.vadim_nuclight>