Re^2: Why is perl not honouring SIGSTOP?

I'm on Ubuntu . Isn't OS supposed to STOP the process for SIGSTOP(the process is put in a TASK_STOPPED state)?

The SIGKILL and SIGSTOP signals cannot be explicitly ignored or caught, and thus their default actions must always be executed. Therefore, SIGKILL and SIGSTOP allow a user with appropriate privileges to destroy and to stop

seems actually not a perl question, but anyone knows the reason?

Comment on Re^2: Why is perl not honouring SIGSTOP?

Replies are listed 'Best First'.
Re^3: Why is perl not honouring SIGSTOP? by Marshall (Canon) on Mar 10, 2012 at 04:29 UTC
SIGSTOP (19) - Stop process is an OS function. Perl plays (normally) no role in this. Of course it is possible to make a program do things like my text editor which interprets CTL-Z to mean "undo the last change". But basically, no Perl doesn't have anything to do with that.	[reply]
Re^3: Why is perl not honouring SIGSTOP? by Marshall (Canon) on Mar 10, 2012 at 05:14 UTC
Well, I don't know but there may some strange behavior related to how Ubuntu handles sleep? If you put your Perl program into an tight loop, or have it do an blocking IO operation or have it read a big disk file line by line, I betcha CTL-Z will do something. Is this a real application question or just intellectual curiosity? Perl itself is not going to do anything with CTL-Z without a lot more code than 2 lines!	[reply]