logread -f does not respond to SIGPIPE
rep.dot.nop at gmail.com
Sat Jul 27 13:59:51 UTC 2013
On 27 July 2013 12:44:16 Frank Rosquin <frank.rosquin at gmail.com> wrote:
> So is anyone interested in this? Is it being tracked in some way?
You could file a bug in bugs.Busybox.net or, even better, see the FAQ on
how to send tested patches.
> On Fri, Jul 5, 2013 at 11:52 PM, Frank Rosquin <frank.rosquin at gmail.com> wrote:
> > Hi,
> > when spawning an instance of logread -f from a script, if the parent
> > script dies/gets killed, logread never exits even though it gets sent
> > SIGPIPE
> > The general consensus seems to be to add ```signal(SIGPIPE,
> > interrupted);``` below line 99 above. This is not my idea, as my C
> > knowledge is minimal.
> > As a point of reference, tail -f does exist under the same circumstances.
> > As requested by sh4rm4 and landley on #busybox, I am submitting this
> > issue here on the mailing list.
> > If you need more information, i will supply what I can.
> > Much obliged.
> > --
> > Frank Rosquin
> Frank Rosquin
> busybox mailing list
> busybox at busybox.net
Sent with AquaMail for Android
More information about the busybox