[ale] Signal trapping

[Leam Hall]

The issue was that the signal mentioned in the output wasn't exactly the
signal needed. The clue was in the phrase "Real-time", and I finally found
a list of RT signals at
https://www.tutorialspoint.com/unix/unix-signals-traps.htm. See the "List
of Signals". Since SIGRTMIN is Signal 34, and I was getting "Real-time
Signal 29", that meant ( 34 + 29) a Signal 63. Or SIGRTMAX-1, since
SIGRRTMIN+29 didn't work.

   trap '' SIGRTMAX-1

Now my brain is fried. Still, it was fun, and I got paid for it!

Leam






On Fri, Jun 12, 2020 at 2:06 PM Michael Potter <michael at potter.name> wrote:

>
> Try calling a function that does not do anything, or put the bash null
> statement in the quotes
>
> trap donothing 29
>
> function donothing {
> :
> }
>
> or trap ':' 29
>
> On Fri, Jun 12, 2020 at 1:23 PM Leam Hall via Ale <ale at ale.org> wrote:
>
>> Anyone know how to trap a signal so that it doesn't echo out to the CLI?
>> I'm using:
>>
>>   trap '' 29
>>   sleep 8 &
>>   pkill -63 -f 'sleep 8' >/dev/null 2>&1
>>
>> but still getting:
>>
>> line 97:  3117 Real-time signal 29     sleep 8
>>
>> Leam
>> _______________________________________________
>> Ale mailing list
>> Ale at ale.org
>> https://mail.ale.org/mailman/listinfo/ale
>> See JOBS, ANNOUNCE and SCHOOLS lists at
>> http://mail.ale.org/mailman/listinfo
>>
>
>
> --
> Michael Potter
>   Tapp Solutions, LLC
>    www.tappsolutions.com
> +1 770 815 6142  ** Atlanta ** michael at potter.name  **
> www.linkedin.com/in/michaelpotter
> Schedule a meeting with me: https://calendly.com/michael-potter
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.ale.org/pipermail/ale/attachments/20200612/1c11e973/attachment.html>