Fixed refer(1) pathname problem.
[unix-history] / usr / src / old / implogd / implogd.8
CommitLineData
b42074ab 1.\" Copyright (c) 1983, 1991 The Regents of the University of California.
512680c9 2.\" All rights reserved.
c0c5c666 3.\"
e7d25f37 4.\" %sccs.include.redist.man%
c0c5c666 5.\"
b42074ab 6.\" @(#)implogd.8 6.7 (Berkeley) %G%
512680c9 7.\"
b42074ab
CL
8.Dd
9.Dt IMPLOGD 8
10.Os BSD 4.2
11.Sh NAME
12.Nm implogd
13.Nd
14.Tn IMP
15logger process
16.Sh SYNOPSIS
17.Nm implogd
18.Sh DESCRIPTION
19.Nm Implogd
20is program which logs error messages from an
21.Tn IMP ,
c0c5c666 22placing them in the file
b42074ab
CL
23.Pa /var/log/implog .
24.Pp
c0c5c666
KM
25Entries in the file are variable length. Each log
26entry has a fixed length header of the form:
b42074ab 27.Bd -literal -offset indent
c0c5c666
KM
28struct sockstamp {
29 short sin_family;
30 u_short sin_port;
31 struct in_addr sin_addr;
32 time_t sin_time;
33 int sin_len;
34};
b42074ab
CL
35.Ed
36.Pp
37followed, possibly, by the message received from the
38.Tn IMP .
743b41d8
KB
39Each time the logging process is started up it places a
40time stamp entry in the file (a header with
b42074ab 41.Ar sin_len
c0c5c666 42field set to 0).
b42074ab
CL
43.Pp
44The logging process will catch only those messages from the
45.Tn IMP
743b41d8
KB
46which are not processed by a protocol module, e.g. IP.
47This implies the log should contain only status information such
b42074ab
CL
48as
49.Dq Tn IMP No going down
50messages,
51.Dq host down
52and other error messages,
53and, perhaps, stray
54.Tn NCP
55messages.
56.Sh SEE ALSO
57.Xr imp 4 ,
58.Xr implog 8
59.Sh HISTORY
60The
61.Nm
62command appeared in
63.Bx 4.2 .