Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: redirecting stdio/stderr from a suspended then bged job
- X-seq: zsh-users 2222
- From: mason@xxxxxxxxxxxxxxx (Geoff Wing)
- To: zsh-users@xxxxxxxxxxxxxx
- Subject: Re: redirecting stdio/stderr from a suspended then bged job
- Date: 12 Mar 1999 05:06:45 GMT
- Mailing-list: contact zsh-users-help@xxxxxxxxxxxxxx; run by ezmlm
- Organization: PrimeNet Computer Consultants
- References: <19990311105427.A6589@xxxxxx>
- Reply-to: mason@xxxxxxxxxxxxxxx
Michael Barnes <mibarnes@xxxxxx> typed:
:This has been bugging me for a while. How can I suspend a job that is
:taking longer than I expect and then put it in the background and then
:redirect stdio and/or stderr to a file (or /dev/null) ?
:example:
:wget http://slowserver/bigfile.tgz
:1% done and its been 2 minutes
:^Z
:zsh: 25317 suspended wget http://slowserver/bigfile.tgz
:bg %1 >/dev/null 2>&1
:nope does not work that just redirects the output of bg not the job that
:was bged.
You can't. It's out of our control unless zsh was to keep running
just to keep the pipes going.
Of course, with recent wget you don't need to (if you use
the -v option) as it will automagically start writing to ``wget-log''
when it can't write to the tty any more. Well, that's what happens
with me. Maybe it needs another option. BTW, the manual says it's
in -v mode by default, but without it I couldn't get it to go to
wget-log (when I tried just now).
Regards,
--
Geoff Wing <gcw@xxxxxxxxx> Mobile : (Australia) 0412 162 441
Work URL: http://www.primenet.com.au/ Ego URL: http://pobox.com/~gcw/
Messages sorted by:
Reverse Date,
Date,
Thread,
Author