Hacker News Reader

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.

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.

You can view a process's logs with 'tail' from any terminal.

But not stdout/stderr.

If you're on systemd, all stdout/err is sent to the journal.

'disown' to detach the daemon from the controlling terminal?