Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: named pipes blocking zsh

X-seq: zsh-users 8931
From: "Tim K. (Gmane)" <tk-gmane+at@xxxxxxxxx>
To: zsh-users@xxxxxxxxxx
Subject: Re: named pipes blocking zsh
Date: Wed, 01 Jun 2005 08:24:19 -0700
In-reply-to: <1050601144728.ZM11059@xxxxxxxxxxxxxxxxxxxxxxx>
Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
References: <d7kfuc$gem$1@xxxxxxxxxxxxx> <1050601144728.ZM11059@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: news <news@xxxxxxxxxxxxx>

Now that I think about it, what if the pine process crashed and didn'thave a chance to send an EOF or remove the pipe (assuming pineimplemented the EOF)? It seems that the read with timeout in zsh shouldwork, it should not just block forever even though a timeout isspecified, but maybe it's not possible to do because it's stuck inopen() not in a read call.


Thanks.


I think this qualifies as a pine bug.  Removing a named pipe will not
by itself send an EOF to any processes that are listening on it.  The
right way for pine to shut down the connection would be to open the fifo,
remove the disk file, then send a final EOF by closing the descriptor.

Anything else is a race condition with the listening process, which may
re-open the fifo for reading before pine has removed it.

References:
- named pipes blocking zsh
  - From: Tim K. (Gmane)
- Re: named pipes blocking zsh
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author