From: steve.simon@snellwilcox.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9p questions
Date: Wed, 23 Jul 2003 16:15:15 +0100 [thread overview]
Message-ID: <9672026969b30fd7ee77df3d0c05137b@yourdomain.dom> (raw)
In-Reply-To: <599525253@snellwilcox.com>
Hi,
Thanks rog for your comments.
I forgot to say the app that caused problems with renaming open files was
CVS, which doesn't bother closing temporary files before moving
them into place.
Just closing the file worked fine here (fd leak in CVS?) and got me using
ncpfs in anger (read thorough testing :-), but a better solution is really
required.
-Steve
next parent reply other threads:[~2003-07-23 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <599525253@snellwilcox.com>
2003-07-23 15:15 ` steve.simon [this message]
2003-07-23 11:13 steve.simon
2003-07-23 14:59 ` rog
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=9672026969b30fd7ee77df3d0c05137b@yourdomain.dom \
--to=steve.simon@snellwilcox.com \
--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).