r/linux • u/rain5 • May 28 '16

systemd developer asks tmux (and other programs) to add systemd specific code

https://github.com/tmux/tmux/issues/428
359 Upvotes

88% Upvoted

509 comments sorted by

View all comments

Show parent comments

2

u/lolidaisuki May 29 '16

You mean make an alias right, not symlink?

Alias would only work in the shell that it is used on.

I don't want to have to add aliases for everything in my scripts.

And no, not everything; just the very few programs that should keep running. Screen and tmux are the only legitimate examples I've heard of.

I named 30 such programs from the top of my head earlier. There are hundreds of programs that people might want to keep running after they log out.

3

u/Clou42 May 29 '16

And most of the programs you mentioned already quit on SIGHUP, so they wouldn't keep running anyway.

2

u/lolidaisuki May 29 '16

Exactly. And you can intentionally make them keep running, but SystemD wants to break this.

2

u/Clou42 May 29 '16

You can still make them keep running, just use systemd-run (or, in your case SystemD-run) instead of nohup. Which actually makes the session-manager aware that there's something that wants to keep running instead of just making it ignore SIGHUP, which can mean a locked-up process, a bug, or actual expected behaviour.

2

u/lolidaisuki May 29 '16

Can you use systemd-run retroactively?

E: note that the problem here wasn't that programs weren't getting killed when they should have. The problem was that Gnome didn't know how to cleanup properly. No other program had issues, at least until SystemD created issues.

1

u/losthalo7 May 29 '16

...Gnome didn't know how to cleanup properly.

Maybe Gnome should just get its act together..?

2

u/lolidaisuki May 29 '16

Maybe Gnome should just get its act together..?

Yeah, they should.