elsen@imecom.imec.be (04/08/91)
Could someone tell me what the following error log entry (uerf)
means (VAX3900,running ultrix 3.1).
This info could be very vital for me , so thanks for any help ,
Marc (elsen@imec.be)
********************************* ENTRY 450. *********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 250. ASCII MSG
SEQUENCE NUMBER 408.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Fri Apr 5 16:00:09 1991 MET DST
OCCURRED ON SYSTEM imec
SYSTEM ID x0A000005 MICROCODE REV = 5.
SYSTYPE REG. x01530301
FIRMWARE REV = 83.
PROCESSOR TYPE KA655
MESSAGE local gen 1424960588
_nlink 0,
********************************* ENTRY 451. *********************************alan@shodha.enet.dec.com ( Alan's Home for Wayward Notes File.) (04/09/91)
In article <1991Apr8.165155.1@imecom.imec.be>, elsen@imecom.imec.be writes: } } Could someone tell me what the following error log entry (uerf) } means (VAX3900,running ultrix 3.1). } } This info could be very vital for me , so thanks for any help , } } Marc (elsen@imec.be) } [ Most of the error log entry deleted... ] } } MESSAGE local gen 1424960588 } _nlink 0, } It comes from nfs_subr.c. It should be preceded by an NFS "stale file handle" message and followed by the Ethernet hardware address of the client. Since I found this in the V4.0 NFS source you might find the message documented in the Kernel Error Message for V4.0 or the NFS documentation. -- Alan Rollow alan@nabeth.cxn.dec.com