On Fri, Mar 09, 2001 at 09:40:51AM +0000, Gavin McCullagh wrote:
>> Hi,
>> quick question here, don't know if this is possible or if anyone
> will have any answers. I frequently run a script which will go for maybe
> acouple of weeks running various computations. Due to the time involved,
> it is sensible use nohup, in order that should I log out, or X gets
> restarted or the network connection to that machine goes down (etc
> etc...), the script keeps going regardless.
Not the question yo uwere asking, but...
If you use bash, there's no need for nohup. Just background the job.
Bash will automatically do the necessary magic to keep the job alive
one the shell quits. I use it regularly for big wget jobs overnight
at the office:
wget <url> &
logout
Come in in the morning, and it's done.
Regarding flushing stdout of another process - don't think there is
any way to do this. The data is buffered in the process's libc, not
in the kernel, so it's a user-land problem, rather than a kernel
issue.
Later,
Kenn
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
