Does `disown` apply only to SIGHUP or some or all the signals? [duplicate]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












-2
















This question already has an answer here:



  • Does a disowned process receive signals other than SIGHUP?

    2 answers



  • Do `disown -h` and `nohup` work effectively the same?

    2 answers



  1. Bash can't send SIGHUP to a disowned job. Is it true for any other
    signal? Does disown apply only to SIGHUP or some or all the
    signals? (I am asking only when Bash sends a signal implicitly, not explicitly. You can always send a SIGHUP explicitly to a disowned job by kill.)

  2. When a disowned job completes, will its parent bash process receive
    SIGCHLD?









share|improve this question















marked as duplicate by Jeff Schaller, Stephen Harris, Rui F Ribeiro, larsks, Stephen Kitt bash
Users with the  bash badge can single-handedly close bash questions as duplicates and reopen them as needed.

StackExchange.ready(function()
if (StackExchange.options.isMobile) return;

$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');

$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();

);
);
);
Jan 4 at 7:30


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.















  • Bash don't send SIGHUP to disowned jobs when exit. But it can send any signal to any process if it want to and has the right permission. All terminated children cause a SIGCHILD send to parent, that's the kernel behavior.

    – 炸鱼薯条德里克
    Jan 4 at 0:39












  • Both questions have not been answered anywhere.

    – Tim
    Jan 4 at 2:22











  • At least the first question is has been asked by yourself before, and you get answer.

    – 炸鱼薯条德里克
    Jan 4 at 2:28











  • Both questions have not been answered (correctly) anywhere.

    – Tim
    Jan 4 at 2:29












  • No questions have not been answers correctly anywhere. They're wrong, I already told you. So, now, answer my question again.

    – 炸鱼薯条德里克
    Jan 4 at 2:31















-2
















This question already has an answer here:



  • Does a disowned process receive signals other than SIGHUP?

    2 answers



  • Do `disown -h` and `nohup` work effectively the same?

    2 answers



  1. Bash can't send SIGHUP to a disowned job. Is it true for any other
    signal? Does disown apply only to SIGHUP or some or all the
    signals? (I am asking only when Bash sends a signal implicitly, not explicitly. You can always send a SIGHUP explicitly to a disowned job by kill.)

  2. When a disowned job completes, will its parent bash process receive
    SIGCHLD?









share|improve this question















marked as duplicate by Jeff Schaller, Stephen Harris, Rui F Ribeiro, larsks, Stephen Kitt bash
Users with the  bash badge can single-handedly close bash questions as duplicates and reopen them as needed.

StackExchange.ready(function()
if (StackExchange.options.isMobile) return;

$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');

$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();

);
);
);
Jan 4 at 7:30


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.















  • Bash don't send SIGHUP to disowned jobs when exit. But it can send any signal to any process if it want to and has the right permission. All terminated children cause a SIGCHILD send to parent, that's the kernel behavior.

    – 炸鱼薯条德里克
    Jan 4 at 0:39












  • Both questions have not been answered anywhere.

    – Tim
    Jan 4 at 2:22











  • At least the first question is has been asked by yourself before, and you get answer.

    – 炸鱼薯条德里克
    Jan 4 at 2:28











  • Both questions have not been answered (correctly) anywhere.

    – Tim
    Jan 4 at 2:29












  • No questions have not been answers correctly anywhere. They're wrong, I already told you. So, now, answer my question again.

    – 炸鱼薯条德里克
    Jan 4 at 2:31













-2












-2








-2









This question already has an answer here:



  • Does a disowned process receive signals other than SIGHUP?

    2 answers



  • Do `disown -h` and `nohup` work effectively the same?

    2 answers



  1. Bash can't send SIGHUP to a disowned job. Is it true for any other
    signal? Does disown apply only to SIGHUP or some or all the
    signals? (I am asking only when Bash sends a signal implicitly, not explicitly. You can always send a SIGHUP explicitly to a disowned job by kill.)

  2. When a disowned job completes, will its parent bash process receive
    SIGCHLD?









share|improve this question

















This question already has an answer here:



  • Does a disowned process receive signals other than SIGHUP?

    2 answers



  • Do `disown -h` and `nohup` work effectively the same?

    2 answers



  1. Bash can't send SIGHUP to a disowned job. Is it true for any other
    signal? Does disown apply only to SIGHUP or some or all the
    signals? (I am asking only when Bash sends a signal implicitly, not explicitly. You can always send a SIGHUP explicitly to a disowned job by kill.)

  2. When a disowned job completes, will its parent bash process receive
    SIGCHLD?




This question already has an answer here:



  • Does a disowned process receive signals other than SIGHUP?

    2 answers



  • Do `disown -h` and `nohup` work effectively the same?

    2 answers







bash signals disown






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 4 at 2:33







Tim

















asked Jan 4 at 0:22









TimTim

26.4k75248457




26.4k75248457




marked as duplicate by Jeff Schaller, Stephen Harris, Rui F Ribeiro, larsks, Stephen Kitt bash
Users with the  bash badge can single-handedly close bash questions as duplicates and reopen them as needed.

StackExchange.ready(function()
if (StackExchange.options.isMobile) return;

$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');

$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();

);
);
);
Jan 4 at 7:30


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.






marked as duplicate by Jeff Schaller, Stephen Harris, Rui F Ribeiro, larsks, Stephen Kitt bash
Users with the  bash badge can single-handedly close bash questions as duplicates and reopen them as needed.

StackExchange.ready(function()
if (StackExchange.options.isMobile) return;

$('.dupe-hammer-message-hover:not(.hover-bound)').each(function()
var $hover = $(this).addClass('hover-bound'),
$msg = $hover.siblings('.dupe-hammer-message');

$hover.hover(
function()
$hover.showInfoMessage('',
messageElement: $msg.clone().show(),
transient: false,
position: my: 'bottom left', at: 'top center', offsetTop: -7 ,
dismissable: false,
relativeToBody: true
);
,
function()
StackExchange.helpers.removeMessages();

);
);
);
Jan 4 at 7:30


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.














  • Bash don't send SIGHUP to disowned jobs when exit. But it can send any signal to any process if it want to and has the right permission. All terminated children cause a SIGCHILD send to parent, that's the kernel behavior.

    – 炸鱼薯条德里克
    Jan 4 at 0:39












  • Both questions have not been answered anywhere.

    – Tim
    Jan 4 at 2:22











  • At least the first question is has been asked by yourself before, and you get answer.

    – 炸鱼薯条德里克
    Jan 4 at 2:28











  • Both questions have not been answered (correctly) anywhere.

    – Tim
    Jan 4 at 2:29












  • No questions have not been answers correctly anywhere. They're wrong, I already told you. So, now, answer my question again.

    – 炸鱼薯条德里克
    Jan 4 at 2:31

















  • Bash don't send SIGHUP to disowned jobs when exit. But it can send any signal to any process if it want to and has the right permission. All terminated children cause a SIGCHILD send to parent, that's the kernel behavior.

    – 炸鱼薯条德里克
    Jan 4 at 0:39












  • Both questions have not been answered anywhere.

    – Tim
    Jan 4 at 2:22











  • At least the first question is has been asked by yourself before, and you get answer.

    – 炸鱼薯条德里克
    Jan 4 at 2:28











  • Both questions have not been answered (correctly) anywhere.

    – Tim
    Jan 4 at 2:29












  • No questions have not been answers correctly anywhere. They're wrong, I already told you. So, now, answer my question again.

    – 炸鱼薯条德里克
    Jan 4 at 2:31
















Bash don't send SIGHUP to disowned jobs when exit. But it can send any signal to any process if it want to and has the right permission. All terminated children cause a SIGCHILD send to parent, that's the kernel behavior.

– 炸鱼薯条德里克
Jan 4 at 0:39






Bash don't send SIGHUP to disowned jobs when exit. But it can send any signal to any process if it want to and has the right permission. All terminated children cause a SIGCHILD send to parent, that's the kernel behavior.

– 炸鱼薯条德里克
Jan 4 at 0:39














Both questions have not been answered anywhere.

– Tim
Jan 4 at 2:22





Both questions have not been answered anywhere.

– Tim
Jan 4 at 2:22













At least the first question is has been asked by yourself before, and you get answer.

– 炸鱼薯条德里克
Jan 4 at 2:28





At least the first question is has been asked by yourself before, and you get answer.

– 炸鱼薯条德里克
Jan 4 at 2:28













Both questions have not been answered (correctly) anywhere.

– Tim
Jan 4 at 2:29






Both questions have not been answered (correctly) anywhere.

– Tim
Jan 4 at 2:29














No questions have not been answers correctly anywhere. They're wrong, I already told you. So, now, answer my question again.

– 炸鱼薯条德里克
Jan 4 at 2:31





No questions have not been answers correctly anywhere. They're wrong, I already told you. So, now, answer my question again.

– 炸鱼薯条德里克
Jan 4 at 2:31










0






active

oldest

votes

















0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes

Popular posts from this blog

Peggy Mitchell

Palaiologos

The Forum (Inglewood, California)