AFS does not support byte-range locking but responds to byte-range locking
calls to lockf and fcntl without error. Instead it prints out these
messages to the console (which are almost always ignored or overlooked)
at each call. Basically, any program that does byte-range locking is
running a little dangerously in AFS space, but personally I have not seen
any problems from this.
(Byte-range locks lock a section of a file; as opposed to whole-file locks
which lock the entire file and are more common).
yuji
----
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
----
On Tue, 21 Jul 1998, Jaeyoung Kim wrote:
>
>
> What does this error message mean? Our AFS client machine (sun4x_55)
> continuously printed out the messages to the console window. It's irritating
> me. How can I stop this message appearing?
>
> afs: byte-range lock/unlock ignore; make sure no one else running this program
>
> --
> ============================================================================
> __/\__ ** Remember Yesterday, Dream about Tomorrow, but ... LIVE TODAY !!!
> \ /\ / -------------------------------------------------------------------
> /_\/_\ ** [EMAIL PROTECTED] http://www.postech.ac.kr/~jay
> \/ ** Jaeyoung Kim Dept. of Computer Science, POSTECH, KOREA
>
Yuji Shinozaki Systems Administrator
[EMAIL PROTECTED] Dept of Physics and Astronomy
http://www.physics.unc.edu Univ. of North Carolina - CH
(919)962-7214 (voice) CB 3255 Philips Hall
(919)962-0480 (fax) Chapel Hill, NC 27599
