[8409] in Info-AFS_Redistribution

home help back first fref pref prev next nref lref last post

RE: Cached write()s, save on close

daemon@ATHENA.MIT.EDU (Jeff Blaine)
Wed Jan 10 18:34:45 2001

Date: Wed, 10 Jan 2001 18:09:20 -0500
From: Jeff Blaine <jblaine@linus.mitre.org>
To: "Neulinger, Nathan R." <nneul@umr.edu>
Cc: info-afs@transarc.com
Message-Id: <4192584538.979150160@jblaine-pc.mitre.org>
In-Reply-To: <F349BC4F5799D411ACE100D0B706B3BB1D39AD@umr-mail03.cc.umr.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

> I believe you can change this as root with the fs storebehind command, but
> I'm not positive.

Actually, no, that's what I thought as well, but that command specifies
that when a close() _is_ finally done, return immediately (or when
some number of K is all that is left to write to the server from cache)
instead of waiting for the data in cache to be fully written to the
server.

>> -----Original Message-----
>> From: Jeff Blaine [mailto:jblaine@linus.mitre.org]
>> Sent: Wednesday, January 10, 2001 3:06 PM
>> To: info-afs@transarc.com
>> Subject: Cached write()s, save on close
>>
>>
>> I could swear that at one point I knew a way around this in AFS.
>>
>> We have a user who is not fond of cached write()s and save-on-close in
>> AFS for a particular file of his.  He also does not have the source
>> code to the tool which is appending to the file, so modifying it to
>> flush is not possible at that level.
>>
>> Any pointers?  I couldn't find anything in the _Managing AFS_ book,
>> the info-afs archives, the FAQ, or the AFS 3.6 docs.


home help back first fref pref prev next nref lref last post