Re: Crontabbing a Ruby script inside a screen

2013-01-24 Thread Volodymyr Kostyrko
24.01.2013 13:27, Dwayne Henderson: Hi, I run this Ruby + Sequel script inside a screen that records data from this live stream 24/7. But it tends to core dump every once in a while, and since I run it in a screen (so it's easy to check in on), I can't really scroll up to catch the error whenever

Re: Crontabbing a Ruby script inside a screen

2013-01-24 Thread Brian Seklecki (Mobile)
screen(1) is just going to fill a massive buffer, then eventually core. You can capture stdout/stderr to a file using script(1) instead. Its basically the same as: % nohup ./command 2>&1 | tee -a ~/command.log & ~BAS On Thu, 24 Jan 2013, Dwayne Henderson wrote: Hi, I run this Ruby + Seq

Re: Crontabbing a Ruby script inside a screen

2013-01-24 Thread Dwayne Henderson
On Thu, Jan 24, 2013 at 1:33 PM, Robert Klemme wrote: > > I am not 100% sure what you want to achieve. But it seems to me that > it would be easier to wrap your Ruby script in something else that > restarts the script if it crashes. Like > > #!/usr/bin/dash > > # no cores > ulimit -c 0 > > while