thanks to all who took their precious time to help (solutions and original
question follows):
Sean O'Connell <sean_at_stat.Duke.EDU>
Joanna Gaski <jgaski_at_WPI.EDU>
Steve Wright (Sys Adm) <wright_at_cs.sc.edu>
Fliguer, Miguel <M_Fliguer_at_miniphone.com.ar>
Yvon Lauriault <yvon.lauriault_at_nlc-bnc.ca>
Dr. Tom Blinn, 603-884-0646 <tpb_at_zk3.dec.com>
Kris Chandrasekhar <Kris.Chandrasekhar_at_digital.com>
alan_at_nabeth.cxo.dec.com
H. Blakely Williford <blakew_at_fullerbrush.com>
Ajay Nautiyal <sxan_at_java.sois.alaska.edu>
Degerness, Mandell ITSD:EX <Mandell.Degerness_at_gems2.gov.bc.ca>
Spalding, Stephen <SSpaldin_at_mem-ins.com>
Mukesh Soni <MSONI_at_tuc.com>
Rodrigo Poblete <rpoblete_at_gmd.com.pe>
Chris Rogers <chrisr_at_kenttec.demon.co.uk>
Nick Batchelor <Nick.Batchelor_at_unilever.com>
Randy Rodgers <rrodgers_at_ci.ft-wayne.in.us>
Brian O'Neill <Brian_ONeill_at_uml.edu>
Marcelo Alonso M. <malonsom_at_villacero.villacero.com.mx>
Biggerstaff, Craig T <Craig.T.Biggerstaff_at_USAHQ.UnitedSpaceAlliance.com>
Emanuel Salazar <Emanuel.Salazar_at_mci.com>
Jim Williams <jim.williams_at_alaska.edu>
Louis <lamullikin_at_ccgate.hac.com>
Hoai Tran <hoai_at_your.abc.net.au>
the overwhelming response was to look in
/var/adm/messages
for the information. this is great, but there was more information to be found
in the /var/adm/binary.errlog file generated by the binlogd utility. this can be
read using the command
# uerf -R -r 300 | more
or some variation thereof.
other responses included:
If you are using a VT class terminals as a console you
can connect a line printer in the back of the terminal
and enable auto-printing. Everything on the terminal
(console) will print. "Yvon Lauriault" <yvon.lauriault_at_nlc-bnc.ca>
If you really want to capture it all and send it to a printer, connect a PC or a
terminal that can divert output to a locally attached printer to the console
serial port.Then run the system with a serial console. You can also use another
UNIX system with "tip" to grab the serial console output. Either way, you can
then divert it to a printer. Or if you have a printing terminal (like a DEC
LA120) you could use that. "Dr. Tom Blinn, 603-884-0646" <tpb_at_zk3.dec.com>
Use a software package such as CA's Console Manager (I think there
are other equivalents on the Internet) Kris Chandrasekhar
<Kris.Chandrasekhar_at_digital.com>
The initial boot information is written to the binary error log and can
be seen via the command:
dia -R | more {JY:works only if you have DEC event loaded}
I usually can see my last boot with the command:
tail -200 /var/adm/messages | more "Degerness, Mandell ITSD:EX"
<Mandell.Degerness_at_gems2.gov.bc.ca>
Most of these messages can be found in
/var/adm/syslog.dated/?/kern.log
{JY:this gives the same info as /var/adm/messages}
"Randy Rodgers" <rrodgers_at_ci.ft-wayne.in.us>
Read the man pages on syslogd and /etc/syslog.conf. The boot messages are
"kern.*" log entries, if I remember correctly. "Biggerstaff, Craig T"
<Craig.T.Biggerstaff_at_USAHQ.UnitedSpaceAlliance.com>
using pcm it is easy, but i will assume no pcm.
{JY: true, no pcm here} Emanuel Salazar <Emanuel.Salazar_at_mci.com>
original message:
does anyone know how to get the information that scrolls past at boot time to be
either written to a file (or is it already?) or sent directly to the printer?
i am running DEC OSF/1 V3.2
thank you all again for taking the time to help
hope to be able to return the favor some day...
josie
*******************************************************************
Josie Young young_at_nuc006.psc.sc.edu
Unix Sys Admin (803) 777 5753
Nuclear Grp
Dept Physics & Astronomy
Univ of SCarolina
Received on Mon May 25 1998 - 21:21:14 NZST