On Tue, 21 Jul 1998, Yuji Shinozaki wrote:
| 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?
This is a good comment. I've long been annoyed by the lack of
timestamps, especially in tracking down problems where the file or
database servers become unavailable for some reason.
I'm not sure about reporting the program name for byte-range locking.
Does the libafs.o module when intercepting lockf() and fcntl() have any
visibility into the name of the program calling it? How about the PID or
other process-table info?
-bws
--
Brian W. Spolarich - ANS Communications - [EMAIL PROTECTED] - 734-214-7311
"Not a whit, we defy augury." - Hamlet, V, ii
