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.

Reply via email to