Possible to use both a monitor and the serial management card or ttyb?
I asked this question in on of the Administration forums, but I think this might be a more appropriate place.
I have a SunFire V440 with an XVR-100 graphics card and LCD monitor. What I'd like is to use the either the serial management port or the other serial port as the system console (i.e. get all console messages here, either on a connected terminal or ideally, logged to another machine running something like conserver) but still be able to use the graphics monitor for X apps etc.
Is this possible? I understand that OBP can only use one device as the console, but I'm unsure as to whether that precludes me from setting the output-device to ttya or ttyb and still using the attached monitor.
Any help would be greatly appreciated. Thanx,
- Darryl
[789 byte] By [
g011um] at [2007-11-26 10:18:09]
# 1
Quick and easy fix:
You could create a startup script that would kick off at boot.
tail -f /var/adm/messages > /dev/ttya
You might want to also investigate the possibility of modifying your /etc/syslog.conf file to include /dev/ttya.
Note: This will only allow you to log/monitor the ouput of messages.
It will NOT give you a console login.
Sun4u at 2007-7-7 2:14:02 >
# 2
There is a nice Sun doc that explains how to set this up by changing input-device and output-device to ttya and modifying your dt config and logindevperm.
Keywords: dtlocal logindevperm
Note: You will no longer be able to login at the Monitor/keyboard directly as root (Not on console)....only the ttya port.
Sun4u at 2007-7-7 2:14:02 >
# 3
> You might want to also investigate the possibility of
> modifying your /etc/syslog.conf file to include
> /dev/ttya.
>
> Note: This will only allow you to log/monitor the
> ouput of messages. It will NOT give you a console login.
That would be perfect actually. What I want is to log console messages on another machine and ideally still have the attached monitor and keyboard work as is.
The reason is that the machine has recently taken to spontaneously rebooting itself, and in such a way that it seems some messages aren't making it to /var/adm/messages (not being flushed to disk before the machine dies?). It's a production server so I'd rather not take it down or have it do all the boot diagnostics on crash/reboot (at least not yet). I'd like to see what messages it's generating just before it's death first.
Thanks for the 2 great replies.
- Darryl
# 4
Daryl,
You might want to check this with Sun Support. We had some early V440's with a problem sounding similar to yours. From memory it ended up the CPU was being reset due to the network interface. I think if you don't use Ethernet0 you didn't have the problem so the solution was to move to the second internal interface or use an internal card for network.
There may be a more permanent correction by now.
bradl at 2007-7-7 2:14:02 >
