Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: Starting daemon using ssh

Subject: Re: Starting daemon using ssh
Date: Thu, 4 Nov 2004 11:28:06 +0000
On Tue, 2 Nov 2004 08:19:39 +0100, Binninger, Martin
<martin.binninger@burdadigital.de> wrote:

While trying, to start a daemon on a remote machine using ssh, the client
doesn't return to the local prompt after performing the start-up of the
daemon. I'm using openssh 3.7.1p2, ssh-version 2.0 on Tru64 as the os.

The command, I'm executing is the following:
ssh -i <KEY> <USER>@<SERVER> "/usr/local/bin/sudo /<PATH>/daemon start &&
echo 'done' "

'done' is being printed, so the daemon is returning control to the shell.

A process on the remote machine may have a lock on the ssh session.
Often this is stdin on the daemon. You could verify this by listing the
file descriptors for the daemon (not sure how to do that on Tru64.).

Workaround:
ssh -i <KEY> <USER>@<SERVER> "<REMOTE CMD> </dev/null >/dev/null 2>/dev/null"

If you start multiple background processes from a single ssh, redirect
each process
individually.

Regards,
-- 
Kieran Tully, Software Developer and Tenor
Reply to Kieran.Tully AT acm.org
http://kieran.tul.ly  http://www.cs.tcd.ie/~tullyka

<Prev in Thread] Current Thread [Next in Thread>