2

As far as I know, nohup signals ignores SIGHUP signal sent by the terminal to the application but the application can change that.

I'm running Spotify through the command nohup spotify & and when I close the terminal by clicking the X symbol on the top corner of the terminal, so does Spotify.

  1. Does this mean Spotify changes it so that it won't ignore SIGHUP signal?
    However, when I close the terminal using exit command, Spotify remains working.

  2. Is the terminal sent different signal when exit command is called? I'd expect the Spotify to terminate as well.

P.S. I am using Elementary OS Loki and xterm.

Improve this question
6
  • 1
    The usual pitfall is that the application exits because its output has been closed. You might try redirecting its output (including stderr) to /dev/null (ditto for its input). Commented Sep 30, 2017 at 15:24
  • @ThomasDickey,s hint is wrong in this case because nohup already handles io, and this does not account for exit working correctly. Commented Sep 30, 2017 at 15:45
  • @ThomasDickey I tried your suggestion just in case but all is same. Also as hildred pointed out, the output goes to nohup.out Commented Sep 30, 2017 at 16:01
  • @ThomasDickey I knew your name was familiar, I was just checking xterm's Wikipedia page and saw that you are maintaining it. I'd like to know your input further on it. Commented Sep 30, 2017 at 16:09
  • 1
    gnome-terminal suffers from this same issue, see bugzilla.gnome.org/show_bug.cgi?id=168320 and its duplicates. Redirecting the three standard file descriptors to /dev/null doesn't change a thing for me. I'd also love to understand what is exactly going on, I haven't had time to track it down. You can use disown, e.g. nohup spotify & disown (probably nohup isn't even needed then) as a workaround. Commented Oct 1, 2017 at 21:52

1 Answer 1

Reset to default
1

Now since you did not say which terminal you were using, I cannot be sure, but The terminal is probably sending a SIGTERM or something else instead of a SIGHUP when it is closed. Three things to do are to read the man page for your terminal emulator, try a different terminal emulator, and to file a bug report on the terminal emulator.

P.S. Which terminal emulator are you using?

Improve this answer
2
  • I tagged it with xterm but it is easy to miss so I edited the question as well. Commented Sep 30, 2017 at 15:54
  • Well xterm's man page says that it sends SIGHUP when the quit action is invoked, but it also has actions to send any signal and I did not see which is called when it gets a destroy event from the window manager. This may be something you can adjust with resources, but I don't know for sure. Commented Sep 30, 2017 at 16:03

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.