On Mon, Mar 31, 2008 at 3:25 PM, Wade Curry <[EMAIL PROTECTED]> wrote:
> Brad Beyenhof([EMAIL PROTECTED])@Mon, Mar 31, 2008 at 09:32:06AM -0700:
>
> > So I've got a bash script (run as a cron job) that currently runs tar
> > and redirects stdout and stderr to particular files.
> >
> > I'd like to run the tar command through screen so that I can check in
> > on the process; also, the archive now spans two tapes, so using screen
> > will hold the process so I can swap manually and respond interactively
> > to tar's request for a new tape. To do this, I first tried just
> > prepending screen to the existing command:
> >
> > /usr/bin/screen -dm tar [options] 2>{$file1} | tee {$file2}
>
> <snip>
>
> I can't experiment at the moment to figure this out, but I'm
> curious what you see when you turn on screen's logging. Anything
> informative perhaps?
After reading docs, it looks like screen logs to one specific default
file (it can be changed, but probably not flexibly enough for me). In
any case, I already did what SJS first suggested. The backup_full
script is already called from backup_master (depending on whether it's
Saturday), so I just paired the screen command with the script call
instead of the tar command.
/me crosses his fingers and waits for Saturday...
--
Brad Beyenhof http://augmentedfourth.com
If they can get you asking the wrong questions, they don't have to worry
about the answers.
~ Thomas Pynchon, writer (1937- )
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
