home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!ogicse!hp-cv!hp-pcd!news1.boi.hp.com!cupnews0.cup.hp.com!wk
- From: wk@cup.hp.com (Wayne Krone)
- Newsgroups: comp.sys.hp
- Subject: Re: /usr/adm/diag ?
- Message-ID: <Brx2qx.FKs@cup.hp.com>
- Date: 24 Jul 92 23:32:56 GMT
- Article-I.D.: cup.Brx2qx.FKs
- References: <1992Jul23.142632.10328@marcal.uucp>
- Sender: news@cupnews0.cup.hp.com
- Distribution: usa
- Organization: HP-UX Kernel Lab, Cupertino
- Lines: 32
- X-Newsreader: Tin 1.1 PL3
-
- marc@marcal.uucp (Marc Veeneman) writes:
- : wk@cup.hp.com (Wayne Krone) writes:
- :
- : >Have HP Support review the log files.
- :
- : Is there software on the system that'll interpret them? Why
-
- Run:
-
- $ sysdiag
- DUI >logtool
- LOGTOOL>list log=NNNN
- LOGTOOL>exit
- DUI >exit
-
- where NNNN is the numeric part of the log file name. Type "help" and
- "help COMMAND" (where COMMAND is one of the commands shown by "help") to
- get more info.
-
- However, the data dumped out often requires knowledge of SCSI protocol
- or such to interpret which is why I suggested contacting HP Support.
-
- logtool is safe (as far as I know) but the other diagnostic utilities
- available via sysdiag can mess up your system if misused.
-
- : Or is a
- : LOGnnnn file always a sign of some impending disaster?
-
- Not necessarily. For example, a non-empty log file (log files 40 bytes
- long are empty) might have a record from a disk which properly handled a
- bad sector by reallocating it. But if a disk has very many such records
- then it should be examined for possible repair/replacement.
-