|
|
1.1 root 1: .\" Copyright (c) 1983 Regents of the University of California.
2: .\" All rights reserved. The Berkeley software License Agreement
3: .\" specifies the terms and conditions for redistribution.
4: .\"
5: .\" @(#)implogd.8c 6.2 (Berkeley) 5/22/86
6: .\"
7: .TH IMPLOGD 8C "May 22, 1986"
8: .UC 5
9: .SH NAME
10: implogd \- IMP logger process
11: .SH SYNOPSIS
12: .B /etc/implogd
13: [
14: .B \-d
15: ]
16: .SH DESCRIPTION
17: .I Implogd
18: is program which logs error messages from the IMP,
19: placing them in the file
20: .IR /usr/adm/implog .
21: .PP
22: Entries in the file are variable length. Each log
23: entry has a fixed length header of the form:
24: .PP
25: .ta 0.5i 1.0i 1.5i
26: .nf
27: struct sockstamp {
28: short sin_family;
29: u_short sin_port;
30: struct in_addr sin_addr;
31: time_t sin_time;
32: int sin_len;
33: };
34: .fi
35: .PP
36: followed, possibly, by the message received from the
37: IMP. Each time the logging process is started up it
38: places a time stamp entry in the file (a header with
39: .I sin_len
40: field set to 0).
41: .PP
42: The logging process will catch only those message from
43: the IMP which are not processed by a protocol module,
44: e.g. IP. This implies the log should contain only
45: status information such as ``IMP going down'' messages,
46: ``host down'' and other error messages,
47: and, perhaps, stray NCP messages.
48: .SH "SEE ALSO"
49: imp(4P),
50: implog(8C)
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.