From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] Replica/pull weirdness?
Date: Mon, 17 Feb 2003 00:52:34 -0500 [thread overview]
Message-ID: <200302170552.h1H5qYM16586@augusta.math.psu.edu> (raw)
Imagine the following scenario:
If replica/pull runs, and the server connection dies for some weird
reason, it's possible that pull will try to remove the client log file
and error out and die. If that's the case, the next time pull runs,
it'll try and remove the client log file again. However, this time,
it won't be able to because the client log file won't exist. The
must function will see rm fail and cause pull to fail. The solution
will be for someone to touch the client log file and run pull again,
but it'll be pretty confusing initially. Shouldn't the
``must rm $clientlog'' line in pull be ``must rm -f $clientlog''
instead?
- Dan C.
reply other threads:[~2003-02-17 5:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200302170552.h1H5qYM16586@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--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).