Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Jianshi Huang
December 6, 2010, 3:07 am
rate this thread
I'm using ssh for launching and communicating with remote processes,
and I want the remote process to terminate whenever ssh terminated
(say SIGTERM or even SIGKILL) or connection dropped.
Currently, the quit mechanism is based on catching EOF in stdin and
write errors in stdout. Is that good enough? Do I still need to trap
particular signal like SIGHUP?
And is it possible that the remote sshd process will hang and pipes
will not be closed and the remote process will get blocked
- » Working sshd_config to restrict root logins to designated hosts
- — Previous thread in » Secure Shell Forum
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — Newest thread in » Secure Shell Forum