From: Joachim Worringen <joachim@ccrl-nece.de>
To: nfs@lists.sourceforge.net
Subject: Re: multiple processes appending data to a single file
Date: Tue, 22 Mar 2005 18:39:09 +0100 [thread overview]
Message-ID: <4240583D.5020602@ccrl-nece.de> (raw)
In-Reply-To: <1111510241.16492.1.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> ty den 22.03.2005 Klokka 17:45 (+0100) skreiv Joachim Worringen:
>
>>Dear NFS experts,
>>
>>I posted the problem description below to comp.protocols.nfs without a
>>real response (only one "it should work" reply - but it doesn't...). So,
>>here comes the problem, below are my questions.
>
> Can you post the offending code? I agree that a scheme such as you
> describe can be made to work, but the devil is in the details...
Your request makes sense, but unfortunately, I can not post the code
right now (although it is straightforward) - unresolved IP issues... :-(
Joachim
--
Joachim Worringen - NEC C&C research lab St.Augustin
fon +49-2241-9252.20 - fax .99 - http://www.ccrl-nece.de
-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2005-03-22 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 16:45 multiple processes appending data to a single file Joachim Worringen
2005-03-22 16:50 ` Trond Myklebust
2005-03-22 17:39 ` Joachim Worringen [this message]
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=4240583D.5020602@ccrl-nece.de \
--to=joachim@ccrl-nece.de \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.