>> Get a lock on a different file than the one you're trying to append
>> to.
>
>I thought of this solution already. Two reasons why it doesn't help:
>
>1. Mail handlers typically lock the folder, not some other file. I know
>there is /usr/spool/mail/user.lock, but this doesn't help as not all
>the folders I am dealing with are somebody's system mailbox.
>
>2. As afsd works asynchronously, if I release the lock on file B after
>closing file A there is probably no guarantee for the file server and
>for other AFS clients to see that information in the same order.
>
Don't know if I am missed the mark here but I think you have to close
the file after you unlock to make sure the cache manager keep thing
consistent. Also check the errors return from the close to make sure
that it is indeed closed.
_____
Phi H. Truong "Hmmmmmmmmm....... "
[EMAIL PROTECTED] ISU Computation Center
Systems Analyst 237 Durham Center ph: (515) 294 - 1420
