Date: Thu, 24 Jan 2013 11:43:30 -0500 (EST) From: "Brian Seklecki (Mobile)" <lavalamp@spiritual-machines.org> To: Dwayne Henderson <its.code.in.here@gmail.com> Cc: ruby-talk@ruby-lang.org, questions@freebsd.org Subject: Re: Crontabbing a Ruby script inside a screen Message-ID: <alpine.LRH.2.00.1301241140590.6438@ecs00.cozzaenterprises.com> In-Reply-To: <CAOOO88C9p7GRFsC12SRHq_62sM%2BQJjwKgAH%2BDbtxANZOO0%2Bpng@mail.gmail.com> References: <CAOOO88C9p7GRFsC12SRHq_62sM%2BQJjwKgAH%2BDbtxANZOO0%2Bpng@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 + 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 it happens. > > So how do I crontab the screen with the Ruby s
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LRH.2.00.1301241140590.6438>