IMPLOGD(8) System Manager's Manual IMPLOGD(8)NAME
implogd - IMP logger process
SYNOPSIS
/usr/sbin/implogd [ -d ]
DESCRIPTION
Implogd is program which logs error messages from the IMP, placing them in the file /usr/adm/implog.
Entries in the file are variable length. Each log entry has a fixed length header of the form:
struct sockstamp {
short sin_family;
u_short sin_port;
struct in_addr sin_addr;
time_t sin_time;
int sin_len;
};
followed, possibly, by the message received from the IMP. Each time the logging process is started up it places a time stamp entry in the
file (a header with sin_len field set to 0).
The logging process will catch only those message from the IMP which are not processed by a protocol module, e.g. IP. This implies the log
should contain only status information such as ``IMP going down'' messages, ``host down'' and other error messages, and, perhaps, stray NCP
messages.
SEE ALSO imp(4P), implog(8C)4.2 Berkeley Distribution November 16, 1996 IMPLOGD(8)
Check Out this Related Man Page
strerr(8) System Manager's Manual strerr(8)NAME
strerr - Receives error messages from the STREAMS log driver
SYNOPSIS
/usr/sbin/strerr [-a sys_admin_mail_name] [-d logdir]
PARAMETERS
Specifies the mail name of the user to receive the message via mail. This is the system administrator by default. Specifies the directory
to contain the error log file. This is /var/adm/streams by default.
DESCRIPTION
The strerr daemon receives error messages from the STREAMS log driver (strlog) for addition to the STREAMS error log files (error.mm.dd) in
the STREAMS error logger directory (/var/adm/streams by default). When first called, the strerr daemon creates the log file error.mm.dd.
This is a daily log file, where mm indicates the month and dd indicates the day of the logged messages. The strerr daemon then appends
each error message that it subsequently receives from the STREAMS log driver to the log file.
STREAMS error log messages have the following format: seq_num std_time ticks_time flags mod_ID sub_ID msg_text where: The error
sequence number. The time the message was sent, in the format hh:mm:ss. The time the message was sent, measured in machine ticks since
the last boot. Can be any of the following indicators: Indicates that the message has also been saved in the process's trace log. Indi-
cates that the message signaled a fatal error. Indicates that the message is to be sent to the system administrator or specified user via
mail. The module identification number of the trace message source. The subidentification number of the trace message source. The trace
message text.
The strerr daemon will run continuously until terminated by the user.
FILES
The error log file or files on which strerr operates.
NOTES
Only one strerr process can open the STREAMS log driver at a time. This restriction is intended to maximize performance.
The STREAMS error logging mechanism works best when it is not overused. The strerr daemon can degrade STREAMS performance by affecting the
response, throughput, and other behaviors of the drivers and modules that invoke it. The daemon will also fail to capture messages if
drivers and modules generate messages at a higher rate than its optimum read rate. Missing sequence numbers among the messages in a log
file indicate that messages have been lost.
RELATED INFORMATION
Interfaces: strlog(7). delim off
strerr(8)
RULES OF THE UNIX AND LINUX FORUMS
For the latest version of the community rules (the official community rules page), please visit here.
No flames, shouting (all caps), sarcasm, bullying, profanity or arrogant posts.
No negative comments about others or impolite remarks. Be patient. No... (1 Reply)
I see lot of ad-hoc shell scripts in our servers which don't have a shebang at the beginning .
Does this mean that it will run on any shell ?
Is it a good practice to create scripts (even ad-hoc ones) without shebang ? (16 Replies)
Hi everyone,
I know the following questions are noobish questions but I am asking them because I am confused about the basics of history behind UNIX and LINUX.
Ok onto business, my questions are-:
Was/Is UNIX ever an open source operating system ?
If UNIX was... (21 Replies)
Dear all,
I use awk quite a bit for data wrangling ... today I find weird behavior that I cannot wrap my head around.
if I execute the following command (simplified to illustrate the behavior ... nothing to do with the real command)
bash-3.2$ awk... (3 Replies)
I have a file hello.txt which i wish to send as a email body (not attachment).
cat -ev hello.txt
1$
2$
3$
I use the following command to send the hello.txt as the email body.
mailx -s "Alert" myteam@mycomp.com<hello.txt
However, the email received has this in the email body
123... (2 Replies)
I've "installed" LM 19.1 to a PNY 16Gb(2.0) pendrive. I have a few issues that I'd like to resolve. First and foremost, the O.S. experiences "lagging" issues and to a lesser degree, freezing. Example: Complete "boot-up" (from start to complete "home" page) can take upwards of 7 mins. Then when... (10 Replies)
Morning All
So, I am starting looking into the world of UNIX for a new job (luckily not my primary function!) and I am looking to get stared. Like anything I seem to learn best by trying things out first in an environment but I have a key question:
Currently I use Oracle VirtualBox, can... (8 Replies)
I've installed Slack 14.2 on /dev/sda1 (/dev/sda2 is swap) and FreeBSD 12 on /dev/sda3 and lilo is the boot manager.
FreeBSD slices are as follows;
/ on /dev/ada0S3a, swap on /dev/ada0s3e, /var on /dev/ada0s3b, /tmp on /dev/ada0s3d and /usr on /dev/ada0s3f.
I hesitate to install Solaris 10... (2 Replies)
In a professional environment with traditional application you often want (or are asked) to report the users.
Traditionally there is the who command
who | awk '{print $1}'telnetd or sshd register the users in the utmp file, to be shown with who, w, users, finger, pinky, ...
In addition they... (1 Reply)