Re: cygwin opensshd: how to detach remotely with fork/exec?

Since no one has answered you yet, I'll throw this out. To exec a program in the background with SSH2 on linux, we use this to close off the file numbers of the process being backgrounded. I think it is important to do that, just as if it were a daemon.

my $chan = $ssh2->channel();
$chan->blocking(1);

$chan->exec("nohup /home/zentara/perlplay/net/zzsleep > foo.out 2> foo
+.err < /dev/null &");

$chan->send_eof;
[download]

I know the SSH2 libs are not what you are using, but it might help for you to see a correctly setup nohup string.

I'm not really a human, but I play one on earth.
Old Perl Programmer Haiku ................... flash japh

Comment on Re: cygwin opensshd: how to detach remotely with fork/exec? Download Code

Replies are listed 'Best First'.
Re^2: cygwin opensshd: how to detach remotely with fork/exec? by Boldra (Curate) on Dec 17, 2012 at 09:11 UTC
Many thanks for your ideas Zentara. Do you know if there is a difference between the way you are redirecting the standard filehandles and the way I do it in my example with `close`? I've tried both now, and neither seems to solve the detach problem with the cygwin sshd. nohup also doesn't seem to have any meaning to cygwin - but I'm not forcing the connection closed. Maybe I can do that with an alarm? At the moment I'm working with psexec again. I'm repeatedly sending simple psexec commands until one works, and then doing the important command. This seems reasonably reliable, if slow. - Boldra	[reply]

Replies are listed 'Best First'.

Re^2: cygwin opensshd: how to detach remotely with fork/exec?
by Boldra (Curate) on Dec 17, 2012 at 09:11 UTC

Many thanks for your ideas Zentara.

Do you know if there is a difference between the way you are redirecting the standard filehandles and the way I do it in my example with close? I've tried both now, and neither seems to solve the detach problem with the cygwin sshd. nohup also doesn't seem to have any meaning to cygwin - but I'm not forcing the connection closed. Maybe I can do that with an alarm?

At the moment I'm working with psexec again. I'm repeatedly sending simple psexec commands until one works, and then doing the important command. This seems reasonably reliable, if slow.

- Boldra

[reply]