4 ms·
By "system service", I meant analogous to everything under /etc/systemd/system - it should be operated the same way things like networking and printers, etc are
by wallacoloo 10y ago
By "system service", I meant analogous to everything under /etc/systemd/system - it should be operated the same way things like networking and printers, etc are handled.
I actually have some services (like Transmission) in /etc/systemd/system that are run on boot as arbitrary users, and they're completely detached from any user sessions (i.e. logging off will never kill them). It seems comparable to logging in, running `nohup transmission` and logging out, but without the weird "he logged out - how are his processes still running?" confusion.
- digi_owl 10y agoThere is no confusion unless one is clueness about unix.
- wallacoloo 10y agoI didn't come here to be insulted.
- digi_owl 10y agoOk, sorry. I just find the whole session thinking an ill fit for unix, outside of a shorthand for a login process and the shell child process it has spawned. Anything beyond that is just another process.
- khedoros 10y agoWhat, exactly, is confusing about it? It's just how it works, and there are good reasons for it. Screen allows you to do some cool things like keep your session running when you log off, so that you can log back in later and pick up where you left off. Something like a daemon is basically meant to run in the background and never be directly interacted with. It's a different thing to tell a process "hold on; I'll be back later". As an example: I've got some SBCs that are on all the time. It's useful to be able to pop on, pick up where I left off from, do some experiments, then log out, without having to set my environment back up every time I do it. There isn't really a better way to achieve the same goal.