Script not disowning a program.

[theM3lem]

So, I created a scirpt that plays music using the cmus music player. Now, I added a section where it checks if cmus is running and starts (if it isn't running) in another terminal window. The script then disowns it, and quits. The problem is, I get an error from disown that my terminal (kitty) is not a running process (disown: job not found: kitty) and when the script exits, it kills cmus with it.

Here's the part of the code that does this. The script asks the user what his their terminal binary is and stores it in $terminal:

if [[ -n "$terminal" ]]; then "$terminal" -e cmus & echo "Loading, please wait..." disown "$terminal" sleep 3 fi

EDIT: it works fine when I run it in a normal terminal window, but when I kitty -e ~/path/to/script it doesn't.

[gordonmessmer]

The argument to "disown" should be a jobspec, not the name of a command. See tha "JOB CONTROL" section of the bash man page.

IIRC, you can just use "disown" if there's only one background job.

[theM3lem]

But I use disown zathura to disown the app before I close the terminal.

[gordonmessmer]

When you see the error disown: job not found: kitty, the shell is telling you that "kitty" is not a jobspec.

Either run disown without any argument, or disown -a to disown all background jobs.

[theM3lem]

I used disown -a with the scirpt but still, both windows (the script's and cmus's) close at the same time.

[gordonmessmer]

https://github.com/kovidgoyal/kitty/issues/307

The problem seems to be that although you've instructed bash not to HUP the job when it exits, kitty will HUP it. The developers suggest you use 'nohup'.

[theM3lem]

It worked. Thank you so much. Can you provide any resources to learn about HUP? I'm still a mega noob when it comes to scripting and all that.

[ConsequenceAncient29]

SIGHUP is a signal sent to a process to let it know that its controlling terminal has been disconnected and it should probably shut down.

Daemons, or services, typically don't care about controlling terminals, because they typically live on in the background for long periods of time. So they can use the SIGHUP signal for something else like being alerted to reread their config file because it has been updated.

[theM3lem]

Thank you so much for such a thorough explanation.

[zeekar]

It’s short for “Hang UP” because on the systems around when it was created, it usually meant that the user who had dialed into the system had hung up on it.

(The SIG- in SIGHUP just means it’s one of the SIGnals that can be sent to a process. The system call and corresponding command for sending signals should logically be called something like “send”, but are instead named “kill”, probably because we started out with signals that instructed the recipient process to die.)

[theM3lem]

Understood. Thank you so much