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