From: "Tiit Lankots" <t.lankots@aprote.ee>
To: "Sergey Reva" <rs_rlab@mail.ru>,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] rfork
Date: Thu, 6 Jan 2005 15:35:43 +0200 [thread overview]
Message-ID: <opsj6n1ti93anw4g@tiitl.aprote.com> (raw)
In-Reply-To: <59634531.20050106152446@mail.ru>
> rfork(RFPROC|RFNOWAIT|RFCFDG|RFNAMEG|RFENVG);
> execl("/bin/plumb","plumb",-SomeFileName-,0);
rfork() literally forks the process. This snippet of code suggests that
_both_ of your processes afterwards get replaced by /bin/plumb; I think
your intention was to execl() only in the child. Check the man pages.
A new window is created by
echo new > /dev/wctl
see rio(4)
next prev parent reply other threads:[~2005-01-06 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 13:24 Sergey Reva
2005-01-06 13:35 ` Tiit Lankots [this message]
2005-01-06 13:46 ` Sergey Reva
2005-01-06 13:52 ` Nigel Roles
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=opsj6n1ti93anw4g@tiitl.aprote.com \
--to=t.lankots@aprote.ee \
--cc=9fans@cse.psu.edu \
--cc=rs_rlab@mail.ru \
/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).