|
|
DataMuseum.dkPresents historical artifacts from the history of: ICL Comet 32 |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about ICL Comet 32 Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 801 (0x321)
Types: TextFile
Notes: UNIX file
Names: »ctdmesg«
└─⟦26887b7e0⟧ Bits:30009717 Comet 32 harddisk image
└─⟦28c352965⟧ »/a« UNIX Filesystem
└─⟦this⟧ »sys/build/help/ctdmesg«
y|yes - add this to /usr/lib/crontab
no - don't
p|print - print it again
%
The file /usr/adm/messages is conventionally used for messages from
the kernel to the system manager. It works like this: The kernel
writes the messages in an internal buffer and cron periodically (once
every 10 minutes in this case) runs /etc/dmesg which looks into the
buffer and appends new messages to /usr/adm/messages.
You should examine (and truncate) the messages file regularly in order
to discover problems, such as bad disk blocks. Really bad errors are
also printed on the console and are thus seen immediately. Unless the
hardware has been fixed, most of the messages will unfortunately refer
to a non-existent disk error 1 2. You can ignore that one.