I agree emphatically with Yuji. I've always been nervous about what application
was trying to lock byte-ranges. I've had a few calls from EMSL users with the
same concern. Seeing those messages also makes me wish for the implementation
of byte-range locking in AFS, sooner rather than later.
Karl Anderson
EMSL Unix System Administrator
Pacific Northwest National Laboratory
-----Original Message-----
From: Yuji Shinozaki [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, July 21, 1998 6:59 AM
To: Jaeyoung Kim
Cc: [EMAIL PROTECTED]
Subject: Re: byterange lock/unlock ignore?
P.S. I wish AFS's console messages were a bit more descriptive, giving
PIDs and timestamps or at least the identity of the daemon producing the
message... We get probably a handful of these messages byte-range
locking
messages a day on several hosts, but we have yet to figure out what
application is attempting the byte-range locking. There are several
other
server console messages that take experimentation and luck to figure out
what is generating them. Anybody have a good way to identify these?
yuji
----
