I wouldn't recommend the "> /dev/null" command. If you start it remotely,
the stdout and stderr usually (but not always) go to e-mail. This way you
can still see the output and not lose any critical messages...
-Chuck
On Thu, 3 Jun 1999, Philip Heede wrote:
> On Thu, 3 Jun 1999 12:03:25 +0200, [EMAIL PROTECTED] wrote:
>
> >Now I can start mprime remotely through telnet - which works fine.
> >But as soon as I quit the particular telnet-session - mprime quits
> >too.
> >Anybody can give me a hint how do keep mprime running?
>
> Sure..
> I run mprime remotely on a server by using a simple
> "./mprime > /dev/null &" command. The "> /dev/null" suppresses output and
> the "&" makes MPrime run in the background. If you want output in a file
> simply replace "/dev/null" with the filename.
>
> --
> Sincerely,
> Philip Heede
>
>
> ________________________________________________________________
> Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: WWW: http://www.silverlink.net/poke :
: E-Mail: [EMAIL PROTECTED] :
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: Ask Mike! Aviation's response to Dear :
: Abby. http://www.avstarair.com :
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
