From: Joel âcheskyâ Salomon <JoelCSalomon@Gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] handling notes
Date: Wed, 11 Oct 2006 03:52:54 -0400 [thread overview]
Message-ID: <d51987d4ddf2ca9ee29c836579cbc2b8@plan9.jp> (raw)
In-Reply-To: <ee9e417a0610102135x1b717800n644fe8dfe056f6eb@mail.gmail.com>
> Try a bigger file, like /dev/zero.
> Or insert a sleep(500) after the write in cat.
>
> Why either of those would fix the problem is
> an exercise to the reader. ;-)
I tried /lib/keyboard as input, and saw the breadcrumb from program end before the end of output; the parent process dies before the pipe breaks!
I’m putting the sleep(500), properly commented, (what manual section is sleep(500) in? ☺) into cat to get the same effect. Thanks, Russ!
Now for the detection and respawning... I’ll hold off on asking for hints for a little while and try to figure it out myself.
Good nigh— ye flipplin’ gods, it’s already morning! — folks,
--Joel
prev parent reply other threads:[~2006-10-11 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 3:30 Joel “chesky” Salomon
2006-10-11 4:35 ` Russ Cox
2006-10-11 7:52 ` Joel “chesky” Salomon [this message]
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=d51987d4ddf2ca9ee29c836579cbc2b8@plan9.jp \
--to=joelcsalomon@gmail.com \
--cc=9fans@cse.psu.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).