From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] i/o on a hangup channel asymmetry
Date: Sun, 19 Jul 2009 16:22:22 -0400 [thread overview]
Message-ID: <aa01b75ee7abe3efae55025c8a5c0e55@quanstro.net> (raw)
In-Reply-To: <EEAEF7E0-CDF6-41EC-A79D-5234A0DD817A@sun.com>
> Observe:
>
also observe (as ron noted) this happens mostly on
pipes. this would tend to cause pipes to shutdown
from right to left.
; 8c -FVTw roman.c && 8l -o roman roman.8
; {roman | dd >/dev/null} & sleep 7; slay dd|rc
write good
write good
; note: sys: write on closed pipe pc=0x0000270a
write: i/o on hungup channel
; roman > roman.out & sleep 7; rm roman.out
write good
write good
; write: phase error -- directory entry not allocated
---
#include <u.h>
#include <libc.h>
void
notary(void*, char *s)
{
fprint(2, "note: %s\n", s);
noted(NCONT);
}
void
main(void)
{
notify(notary);
for(;;){
if(write(1, "roman", 5) != 5){
fprint(2, "write: %r\n");
exits("write");
}
fprint(2, "write good\n");
sleep(5000);
}
}
prev parent reply other threads:[~2009-07-19 20:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 18:39 Roman V. Shaposhnik
2009-07-19 1:06 ` erik quanstrom
2009-07-19 9:30 ` Charles Forsyth
2009-07-19 20:32 ` Roman Shaposhnik
2009-07-19 21:01 ` Francisco J Ballesteros
2009-07-20 4:49 ` Roman Shaposhnik
2009-07-20 9:53 ` Charles Forsyth
2009-07-20 17:01 ` Roman V Shaposhnik
2009-07-20 18:38 ` Charles Forsyth
2009-07-19 21:11 ` Mechiel Lukkien
2009-07-19 21:55 ` Charles Forsyth
2009-07-20 4:52 ` Roman Shaposhnik
2009-07-20 5:21 ` erik quanstrom
2009-07-20 16:53 ` Roman V Shaposhnik
2009-07-21 1:01 ` erik quanstrom
2009-07-21 2:04 ` Russ Cox
2009-07-21 2:15 ` erik quanstrom
2009-07-23 12:15 ` roger peppe
2009-07-20 9:52 ` Charles Forsyth
2009-07-20 17:14 ` Roman V Shaposhnik
2009-07-19 20:06 ` Roman Shaposhnik
2009-07-19 20:22 ` erik quanstrom [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=aa01b75ee7abe3efae55025c8a5c0e55@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).