3 ms·

The point about not being able to reattach to old screen sessions is a big one. Especially for those who happen to be running daemons in screen. Ill-advised, bu

The point about not being able to reattach to old screen sessions is a big one. Especially for those who happen to be running daemons in screen. Ill-advised, but of course it happens and can be useful sometimes for anything that isn't mission critical.

dingaling 13y ago
Yes, it is very naughty but I find daemon-in-[screen|tmux] to be very useful for monitoring a new daemon's output and keeping an eye on its uptime / robustness. Once we're happy with it we can dispatch it to the depths of init.
- judk 13y ago
  You can view a process's logs with 'tail' from any terminal.
  - sp332 13y ago
    But not stdout/stderr.
    - CUViper 13y ago
      If you're on systemd, all stdout/err is sent to the journal.
judk 13y ago
'disown' to detach the daemon from the controlling terminal?
prg318 13y ago
Running a daemon in screen can also been useful when for whatever reason the daemon accepts commands via stdin. I know a lot of game servers do this. For example, with the Quake3 server you can use stdin to list users, ban users, change maps, and do other things without having to launch a game client and authenticating as a server admin. Although I guess technically if a server process supports interactive input then its not a "daemon" anymore, but I'm not keeping score.