On Mon, Sep 23, 2002 at 04:42:25PM +0300, Peter Pentchev wrote: > On Mon, Sep 23, 2002 at 04:34:18PM +0300, Vladimir Terziev wrote: > > > > Hi hackers, > > > > I'm implementing a programmme, which writes a big amount of data (using >write(2)) to a socket. > > When the communication stream has been closed by some reason, during the >write(2) call, my process receives SIGPIPE. I tryed to catch it with signal(3) and >change the behaviour of write(2) call with siginterrupt(3), but SIGPIPE is still >raised to my process and terminates it. > > > > Any help and ideas will be useful! > > You should receive a short write(2) before the SIGPIPE is sent, most > probably a write() which returns -1 and sets errno to, say, ECONNRESET > or something like that. Are you sure *all* your previous writes return > as many bytes as you have tried to write?
Hit ':wq' too fast ;) You might want to look into scheduling your write(2) calls only when possible, using either select(2) or poll(2) to check the network socket for writability. G'luck, Peter PS. Wow. 'look writa' returned both 'writable' and 'writability'. 'look writea' returned 'writeable', but not 'writeability'. Strike another one for English grammar ;) -- Peter Pentchev [EMAIL PROTECTED] [EMAIL PROTECTED] PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 I've heard that this sentence is a rumor.
msg36998/pgp00000.pgp
Description: PGP signature
