From: Chris Siebenmann <cks>
To: rc
Subject: Re: $pid
Date: Wed, 3 Jun 1992 19:49:27 -0400 [thread overview]
Message-ID: <92Jun3.194943edt.2735@hawkwind.utcs.toronto.edu> (raw)
In-Reply-To: quanstro's message of Wed, 03 Jun 92 19:17:53 -0400. <9206032317.AA27591@stolaf.edu>
Easily fixed, I think; apply the following patch to wait.c. Corrections
by those more widely read in rc internals than me gladly welcome.
- cks
*** /tmp/,RCSt1a17852 Wed Jun 3 19:48:00 1992
--- wait.c Wed Jun 3 19:46:06 1992
***************
*** 44,49 ****
--- 44,50 ----
/* NOTREACHED */
case 0:
forked = TRUE;
+ varassign("pid", word(nprint("%d", getpid()), NULL), FALSE);
SIGCHK;
return 0;
default:
next prev parent reply other threads:[~1992-06-03 23:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-06-03 23:17 $pid Erik Quanstrom
1992-06-03 23:49 ` Chris Siebenmann [this message]
1992-06-05 1:16 ` $pid John Mackin
[not found] <cks@hawkwind.utcs.toronto.edu>
1992-06-04 10:05 ` $pid malte
1992-06-04 12:14 $pid Erik Quanstrom
1992-06-04 16:57 $pid haahr
1992-06-04 17:01 $pid haahr
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=92Jun3.194943edt.2735@hawkwind.utcs.toronto.edu \
--to=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).