rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Markus Friedl <Markus.Friedl@informatik.uni-erlangen.de>
To: luyer@ucs.uwa.edu.au
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: intr and RC
Date: Tue, 11 Feb 1997 08:57:36 -0500	[thread overview]
Message-ID: <199702111357.OAA04676@faui01.informatik.uni-erlangen.de> (raw)
In-Reply-To: <Pine.LNX.3.95.970113084557.14761C-100000@typhaon.ucs.uwa.edu.au> from "David Luyer" at Jan 12, 97 07:52:50 pm

hello!

> Using standard rc-1.4 and "rcp file solaris-machine:" to a recent version
> of Solaris, I get "rc" on the solaris machine hanging taking all CPU in an
> infinite loop (most, if not all the time).
> 
> OS is "SunOS sage 5.5 Generic sun4c sparc SUNW,Sun_4_40" with a variety of
> patches.
> 
> Is this reproducable for you?

I had this problem, too, when 'upgrading' from SunOS4 to Solaris2
and found help in the rc-list archive from 1994:

Solaris rshd (and only Solaris) sets SIGCLD to SIG_IGN and
causes wait.c to loop forever waiting for childs. You can fix
this by forcing SIGCHLD to SIG_IGN in signal.c (about line 70):

	if(i==SIGCHLD && h==SIG_IGN)
		h=SIG_DFL;

hope this helps,

-markus


  reply	other threads:[~1997-02-11 21:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-01-12 23:39 Scott Schwartz
1997-01-13  0:52 ` David Luyer
1997-02-11 13:57   ` Markus Friedl [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-01-13  1:33 Scott Schwartz
1997-01-12 23:17 Byron Rakitzis
1997-01-09 21:59 Scott Schwartz
1997-01-08 20:01 Mark K. Gardner
1997-01-09 11:09 ` Tim Goodwin
1997-01-08  7:45 Bengt Kleberg
1997-01-07 19:55 Alan Watson
1997-01-07 18:00 Alan Watson
1997-01-07 17:03 Mark K. Gardner
1997-01-07 17:16 ` Scott Schwartz
1997-01-07 17:46 ` Paul Haahr
1996-12-31 21:53 Mark K. Gardner
1996-12-31 22:01 ` Soren Dayton

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199702111357.OAA04676@faui01.informatik.uni-erlangen.de \
    --to=markus.friedl@informatik.uni-erlangen.de \
    --cc=luyer@ucs.uwa.edu.au \
    --cc=rc@hawkwind.utcs.toronto.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).