To: Scott Merrilees <Sm@cerberus.bhpese.oz.au>,
The rc Mailing List <firstname.lastname@example.org>
Subject: Re: solaris 2.2 & rshd & rc
Date: Mon, 28 Mar 1994 21:54:26 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
From: Scott Merrilees <Sm@cerberus.bhpese.oz.au>
Subject: solaris 2.2 & rshd & rc
When doing a rsh command to a solaris 2.2 box, I find that the rc
started by rshd hangs in a cpu loop after the command has terminated.
Interestingly, SIGCLD is ingored in both rshd & rc. Has anyone else
fixed this problem ?
it's not that rc _ignores_ SIGCLD, it just doesn't touch it. when rc
is started by login and forks a program, you will notice that SIGCLD
is SIG_DFL. but when rc is started by rshd, it must be set to SIG_IGN.
bad shit happens in sysvr4 when this is done, namely, a parent is not
notified of the death of a child, so rc just sits in that wait loop
waiting to pick up the status of the child it just forked, a status
it will never get. i noticed the cpu in a tight loop when this happened.
anyway, i just hacked the code to make sure SIGCLD is _always_ SIG_DFL.
this seems to fix the problem.
next prev parent reply other threads:[~1994-03-29 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-03-29 2:29 Scott Merrilees
1994-03-29 2:54 ` noel [this message]
1994-03-29 3:13 ` Scott Merrilees
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).