Re: User's cron job creates zombie process on 5.3
Peter Jeremy wrote:
On Wed, 2005-Jan-19 21:14:26 -0800, spam maps wrote:
( /usr/bin/ssh -n -f ${tunnel} )
Alas, no success. Still get the defunct zombie
process.
I actually wonder if this is an odd or buggy
behaviour of ssh, or is cron making a mistake here?
The cron daemon (which will have a PPID of 1) forks
a copy of itself to actually handle the cron job
(I suspect this is the parent of the zombie that
you are seeing). This child process runs
/bin/sh -c CRONJOB (where CRONJOB is the line in
your crontab) and I suspect this is the zombie you
are seeing.
My guess is that your ssh process is holding open
file descriptors and the cron child process is
waiting for these descriptors to close before
wait()ing for the child. If this is true, then you
should avoid it with something like:
( /usr/bin/ssh -n -f ${tunnel} /dev/null 21 )
BINGO!
That works. Zombie has gone. Thank you.
Leaving a zombie process around, means there's a
kind
of bug/mistake somewhere, right?
Yes. But it's not necessarily a bug in FreeBSD :-).
So, after you've given me a complicated solution to
avoid the zombie, can you tell which program is at
error here? Cron, ssh, or FreeBSD?
Rob.
__
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: User's cron job creates zombie process on 5.3
--- Don Lewis [EMAIL PROTECTED] wrote:
On 20 Jan, spam maps wrote:
Peter Jeremy wrote:
My guess is that your ssh process is holding open
file descriptors and the cron child process is
waiting for these descriptors to close before
wait()ing for the child. If this is true, then
you
should avoid it with something like:
( /usr/bin/ssh -n -f ${tunnel} /dev/null 21
)
I suspect that the to put ssh in the background
isn't necessary.
You're right indeed, it also works without the .
Thanks,
Rob.
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: User's cron job creates zombie process on 5.3
--- Darryl Okahata [EMAIL PROTECTED] wrote:
Raymond Wiker [EMAIL PROTECTED] wrote:
Hmm... Maybe this will work?
/bin/sh -c /usr/bin/ssh -n -f ${tunnel}
--- the effect of this should (hopefully) be that
init becomes the
parent of the zombie process.
An easier-to-read way, assuming that a
Bourne-compatible shell is
used (e.g., /bin/sh and not /bin/csh), would be:
( /usr/bin/ssh -n -f ${tunnel} )
Alas, no success. Still get the defunct zombie
process.
I actually wonder if this is an odd or buggy behaviour
of ssh, or is cron making a mistake here?
Leaving a zombie process around, means there's a kind
of bug/mistake somewhere, right?
Regards,
Rob.
__
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
make install problems with OpenSSH
make install fails when building OpenSSH on 3.4-R Here are the errors: === OpenSSH-1.2.2 depends on shared library: crypto.1 - found === OpenSSH-1.2.2 depends on shared library: rsaref.2 - found === Patching for OpenSSH-1.2.2 === Applying FreeBSD patches for OpenSSH-1.2.2 === Configuring for OpenSSH-1.2.2 === Building for OpenSSH-1.2.2 === lib Warning: Object directory not changed from original /usr/ports/security/openssh/work/ssh/lib cc -O -pipe -I/usr/ports/security/openssh/work/ssh/lib/.. -I -I/usr/ports/security/openssh/work/ssh/lib/.. -I/usr/local/usr/include -c /usr/ports/security/openssh/work/ssh/lib/../authfd.c -o authfd.o In file included from /usr/ports/security/openssh/work/ssh/lib/../ssh.h:21, from /usr/ports/security/openssh/work/ssh/lib/../authfd.c:19: /usr/ports/security/openssh/work/ssh/lib/../rsa.h:21: openssl/bn.h: No such file or directory /usr/ports/security/openssh/work/ssh/lib/../rsa.h:22: openssl/rsa.h: No such file or directory In file included from /usr/ports/security/openssh/work/ssh/lib/../ssh.h:22, from /usr/ports/security/openssh/work/ssh/lib/../authfd.c:19: /usr/ports/security/openssh/work/ssh/lib/../cipher.h:19: openssl/des.h: No such file or directory /usr/ports/security/openssh/work/ssh/lib/../cipher.h:20: openssl/blowfish.h: No such file or directory /usr/ports/security/openssh/work/ssh/lib/../authfd.c:27: openssl/rsa.h: No such file or directory In file included from /usr/ports/security/openssh/work/ssh/lib/../ssh.h:21, from /usr/ports/security/openssh/work/ssh/lib/../authfd.c:19: /usr/ports/security/openssh/work/ssh/lib/../rsa.h:25: parse error before `*' /usr/ports/security/openssh/work/ssh/lib/../rsa.h:35: parse error before `*' /usr/ports/security/openssh/work/ssh/lib/../rsa.h:36: parse error before `*' In file included from /usr/ports/security/openssh/work/ssh/lib/../ssh.h:22, from /usr/ports/security/openssh/work/ssh/lib/../authfd.c:19: /usr/ports/security/openssh/work/ssh/lib/../cipher.h:37: parse error before `des_key_schedule' /usr/ports/security/openssh/work/ssh/lib/../cipher.h:37: warning: no semicolon at end of struct or union /usr/ports/security/openssh/work/ssh/lib/../cipher.h:37: warning: no semicolon at end of struct or union /usr/ports/security/openssh/work/ssh/lib/../cipher.h:38: warning: no semicolon at end of struct or union /usr/ports/security/openssh/work/ssh/lib/../cipher.h:39: warning: data definition has no type or storage class /usr/ports/security/openssh/work/ssh/lib/../cipher.h:40: parse error before `key3' /usr/ports/security/openssh/work/ssh/lib/../cipher.h:40: warning: data definition has no type or storage class /usr/ports/security/openssh/work/ssh/lib/../cipher.h:41: parse error before `iv3' /usr/ports/security/openssh/work/ssh/lib/../cipher.h:41: warning: data definition has no type or storage class /usr/ports/security/openssh/work/ssh/lib/../cipher.h:42: warning: data definition has no type or storage class /usr/ports/security/openssh/work/ssh/lib/../cipher.h:44: field `key' has incomplete type /usr/ports/security/openssh/work/ssh/lib/../cipher.h:47: parse error before `}' /usr/ports/security/openssh/work/ssh/lib/../cipher.h:47: warning: data definition has no type or storage class /usr/ports/security/openssh/work/ssh/lib/../cipher.h:48: parse error before `}' /usr/ports/security/openssh/work/ssh/lib/../cipher.h:48: warning: data definition has no type or storage class /usr/ports/security/openssh/work/ssh/lib/../cipher.h:70: parse error before `*' /usr/ports/security/openssh/work/ssh/lib/../cipher.h:78: parse error before `*' /usr/ports/security/openssh/work/ssh/lib/../cipher.h:83: parse error before `*' /usr/ports/security/openssh/work/ssh/lib/../cipher.h:88: parse error before `*' In file included from /usr/ports/security/openssh/work/ssh/lib/../authfd.c:19: /usr/ports/security/openssh/work/ssh/lib/../ssh.h:299: parse error before `RSA' /usr/ports/security/openssh/work/ssh/lib/../ssh.h:317: parse error before `BIGNUM' /usr/ports/security/openssh/work/ssh/lib/../ssh.h:330: parse error before `BIGNUM' /usr/ports/security/openssh/work/ssh/lib/../ssh.h:336: parse error before `BIGNUM' /usr/ports/security/openssh/work/ssh/lib/../ssh.h:384: parse error before `BIGNUM' /usr/ports/security/openssh/work/ssh/lib/../ssh.h:392: parse error before `BIGNUM' /usr/ports/security/openssh/work/ssh/lib/../ssh.h:399: parse error before `*' /usr/ports/security/openssh/work/ssh/lib/../ssh.h:416: parse error before `RSA' /usr/ports/security/openssh/work/ssh/lib/../ssh.h:425: parse error before `RSA' /usr/ports/security/openssh/work/ssh/lib/../ssh.h:437: parse error before `RSA' In file included from /usr/ports/security/openssh/work/ssh/lib/../authfd.c:21: /usr/ports/security/openssh/work/ssh/lib/../authfd.h:72: parse error before `BIGNUM' /usr/ports/security/openssh/work/ssh/lib/../authfd.h:82: parse error before `BIGNUM' /usr/ports/security/openssh/work/ssh/lib/../authfd.h:88:
