No post body was provided.
Ask HN: Good alternatives to screen/tmux to persist long term jobs?
1–8 of 8 posts
Re: Ask HN: Good alternatives to screen/tmux to persist long term jobs?
#2Either write programs that daemonize themselves or write upstart/systemd services
Re: Ask HN: Good alternatives to screen/tmux to persist long term jobs?
#3If it's a one off isn't this exactly what nohup is designed for?
Re: Ask HN: Good alternatives to screen/tmux to persist long term jobs?
#4If it's a one off isn't this exactly what nohup is designed for?
This isn't a one-off; I want a simple solution that requires as little setup as possible. I also want infinite buffer space to store the stdout and stderr of processes, which neither screen nor tmux provide (both require you to preallocate buffer space).
Re: Ask HN: Good alternatives to screen/tmux to persist long term jobs?
#5If it's a one off isn't this exactly what nohup is designed for?
This isn't a one-off; I want a simple solution that requires as little setup as possible. I also want infinite buffer space to store the stdout and stderr of processes, which neither screen nor tmux provide (both require you to preallocate buffer space).
Oh.
Well if it's a daemon type tool, write an init file - either a shell script for sysvinit or a service file for systemd.
Re: Ask HN: Good alternatives to screen/tmux to persist long term jobs?
#6supervisor?
Re: Ask HN: Good alternatives to screen/tmux to persist long term jobs?
#7I can't remember if it has the buffer space you want, but take a look at dtach. https://github.com/djpohly/dtach/blob/master/README
Re: Ask HN: Good alternatives to screen/tmux to persist long term jobs?
#8I can't remember if it has the buffer space you want, but take a look at dtach. https://github.com/djpohly/dtach/blob/master/README
Nevermind, it looks like it doesn't have any buffer space.