Re: imp timeout

Tom wrote:

> would an & after my imp syntax solve this do you think to detach it from
> the console?

No. To add to what the others replied...

By default, certain devices are "connected" to an online process. STDIN, STDOUT, STDERR. Also, the process has the shell process as parent. If the parent dies, it usually takes the children with.

When writing Unix daemons for example, you will do a few things in the process.. you will close the standard devices, you will detach yourself from the parent process, and you will even change filesystems (you do not want the daemon to run on a non-root filesystem that can be unmounted at anytime).

When you use the & to enter a batch job, and it does not perform the above mentioned stuff, it is likely to keel over and die when something "unexpected" happens (like you exiting your telnet session).

There are 3 ways around this as the others have already mentioned.

You can use nohup. This will "daemonize" the process for you.

You can use cron.

You can use the at command (which is often easier to use for an adhoc batch jobs than to use cron).

Just remember that bit about the .profile though - cron does not run .profiles for you.

--
Billy