Hello all,
we use a AlphaStation 600 5/266 as a compute server,
so no keyboard and no monitor is connected directly
to the machine. As a console we use a vt100 on
the serial port.
We upgraded from 3.2C to 4.0b (via steps in between).
Before the upgrade every boot was logged to /var/adm/messages
Now this file shows from the last boot only the following lines:
Jan 27 09:17:02 fphsv01 vmunix: ported
Jan 27 09:17:02 fphsv01 vmunix: cam_logger: CAM_ERROR packet
Jan 27 09:17:02 fphsv01 vmunix: cam_logger: bus 0 target 4 lun 7
Jan 27 09:17:02 fphsv01 vmunix: isp_process_response_queue
Jan 27 09:17:02 fphsv01 vmunix: Unexpected bus free CSEC status reported
Jan 27 09:17:02 fphsv01 vmunix: ADVFS: using 3491 buffers containing 27.27 megabytes of memory
Jan 27 09:17:14 fphsv01 vmunix: SuperLAT. Copyright 1994 Meridian Technology Corp. All rights
reserved.
Jan 27 09:17:28 fphsv01 vmunix: pcxal_init_keyboard: keyboard init unsuccessful
(the CAM errors come from an unsupported tape stacker.)
Where is the rest of the information from this boot? It all scrolled through
on the vt100, but it seems not to be recorded anywhere?
How do I save the information from every boot now?
Do I really have to connect a console printer to the serial port,
as I still have it on my VAX server?
I really hate all these "features" that I have to deal with after the
upgrade... (TeX stopped working, g++ gives warnings, emacs and netscape
both die with "Segmentation fault (core dumped)", the CERN
software PAW++ dies with the same error).
Rainer Landes, eMail: Computer-Administration_at_Physik.uni-karlsruhe.de
Tel(+49)721 608 3578
http://www-comp.physik.uni-karlsruhe.de/
Computer facilities of the Faculty of Physics, Univ. of Karlsruhe, GER
Received on Mon Jan 27 1997 - 18:19:49 NZDT