[PATCH 1/2] allow honouring libc provided SIGRTMIN/SIGRTMAX

haroon maqsood maqsood3525 at live.com
Fri Oct 5 11:42:30 UTC 2018


Did not reply to the group, here is the fixed patch.
it was a stupid mistake on my part.
Thanks
Haroon
________________________________
From: busybox <busybox-bounces at busybox.net> on behalf of Rasmus Villemoes <rasmus.villemoes at prevas.dk>
Sent: Friday, October 5, 2018 7:08 AM
To: busybox at busybox.net
Subject: Re: [PATCH 1/2] allow honouring libc provided SIGRTMIN/SIGRTMAX

On 2018-09-12 16:06, Rasmus Villemoes wrote:
> When an application documents that it responds such and such to
> SIGRTMIN+n, that almost always means with respect to the libc-provided
> SIGRTMIN. Hence I disagree with the "more correct" in commit
> 7b276fc17594. In any case, this is rather unfortunate:
>
> # kill -l RTMIN+2
> 36
> # busybox kill -l RTMIN+2
> 34
>
> (the first shell is bash). We probably can't change default behaviour
> after 7 years, but at least we can provide a config option.

ping
_______________________________________________
busybox mailing list
busybox at busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20181005/53710207/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-fix-format-specifier.patch
Type: text/x-patch
Size: 17694 bytes
Desc: 0001-fix-format-specifier.patch
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20181005/53710207/attachment-0001.bin>


More information about the busybox mailing list