From: Vincent Lefevre <vincent@vinc17.net>
To: zsh-users@zsh.org
Subject: Re: strange behavior
Date: Sun, 30 Jan 2011 01:37:31 +0100 [thread overview]
Message-ID: <20110130003731.GL15921@prunille.vinc17.org> (raw)
In-Reply-To: <110128074915.ZM5855@torch.brasslantern.com>
On 2011-01-28 07:49:15 -0800, Bart Schaefer wrote:
> I forget whether we covered this before, but does {svn "$@"} ever
> fork as part of its execution?
Yes (for SSH connection, and the ssh script can start a SSH master
connection, which will still run in background after svn terminates,
and that's why I needed the svnwrapper:term trick in my script).
> There has to be some kind of race condition here. 2>>(filter) runs
> filter in the background, so if something behind svn also runs as an
> separate process, it could be possible for the filter to exit and
> close it's stdin (thereby closing everything else's stdder) before
> operating-system-level exit-time buffer-flushing has finished.
Yes, this happens, but I don't see why this could make the script
terminate with a broken pipe. I recall the whole script:
filter()
{
unset brpipe
while true
do
unset line timeout
while read -r $timeout -k -u 0 ch
do
line="$line$ch"
[[ $ch = $'\012' ]] && break
timeout=(-t 0.1)
done
case $line in
svnwrapper:term$'\012')
break ;;
*Broken\ pipe$'\012') brpipe=1 ;;
?*) printf "%s" "$line" >&2 ;;
*) break ;; # empty line (end of file) - parent has died?
esac
done
# The "sleep 5" is there to avoid a rare race condition (it occurred
# once): make sure the parent process receives the PIPE signal before
# the filter process terminates (which can yield a SIGPIPE in svn).
[[ -z $brpipe ]] || { kill -PIPE $$; sleep 5 }
}
{ svn "$@"; st=$?; echo "svnwrapper:term" >&2 } 2>>(filter)
exit $st
Because of the "while true" loop, filter should still run after svn
terminates.
Note that when I obtained the "zsh: exit 141", the svn output wasn't
redirected, so that a "Broken pipe" message from svn was not possible.
> Hmm, another thought ... maybe the "zsh: exit 141" is coming from
> the shell's exit-time handling of the "filter" program, rather than
> from svn. I've lost enough context here that I don't recall whether
> that was previously ruled out too.
What do you mean here?
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2011-01-30 0:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 12:09 Vincent Lefevre
2010-11-15 16:32 ` Vincent Lefevre
2010-11-15 17:24 ` Bart Schaefer
2010-11-16 3:10 ` Vincent Lefevre
2011-01-28 14:44 ` Vincent Lefevre
2011-01-28 15:49 ` Bart Schaefer
2011-01-30 0:37 ` Vincent Lefevre [this message]
2011-01-30 22:25 ` Bart Schaefer
2011-01-31 9:11 ` Vincent Lefevre
2011-04-11 14:26 ` Vincent Lefevre
2011-04-11 14:39 ` Vincent Lefevre
2011-04-11 15:15 ` Peter Stephenson
2011-04-28 11:32 ` Vincent Lefevre
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=20110130003731.GL15921@prunille.vinc17.org \
--to=vincent@vinc17.net \
--cc=zsh-users@zsh.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).