Hi
I've written a perl program which, when executed, fork()'s into the
background, doing it's job, so that the ssh session which executed it can be
closed.
The dilemma I have is the program crashes on random occasions due to an
unknown bug which I can't trace. The only method I would have of catchi
dan wrote:
Hi
Hello,
I've written a perl program which, when executed, fork()'s into the
background, doing it's job, so that the ssh session which executed it can be
closed.
The dilemma I have is the program crashes on random occasions due to an
unknown bug which I can't trace.
Maybe it's a
> -Message d'origine-
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] De la part de zentara
> Envoyé : samedi 25 juin 2005 13:36
> À : beginners@perl.org
> Objet : Re: route STDOUT to file
>
>
> There are a whole bunch of different ways, ...
>
John W. Krahn wrote:
dan wrote:
I've written a perl program which, when executed, fork()'s into the
background, doing it's job, so that the ssh session which executed it
can be
closed.
The dilemma I have is the program crashes on random occasions due to an
unknown bug which I can't trace.
I use screen as my tool to deal with unstable network connection.
Its command line version of vncviewer.
Screen dameon allows me to reconnect the previously opened screen,
if I by mistake detache or exit the current shell, or network forces
my connection down.
I assume a non-perlish solution wil
Manish Sapariya wrote:
> I use screen as my tool to deal with unstable network connection.
> Its command line version of vncviewer.
>
> Screen dameon allows me to reconnect the previously opened screen,
> if I by mistake detache or exit the current shell, or network forces
> my connection down.
H
