I see the following message in my dmesg:
" syslogd: /dev/sysmsg: I/O error"
There is another problem that could be associated with this. Veritas
"hastart" does not start both the 'had' and 'hashadow' unless and
untill a laptop is hooked on to the server. if we do a 'truss hastart
-fore' it starts well.
This implies to me that there is some prob with /dev/console.
truss -p had_pid also indicates the same
i think that the above syslogd message also indicates something with
CONSOLE.
does anyone have any insights on this issue? Any suggestion is
appreciated.
Thanks & Regards
Kasthuri.J
1. Log into the 420R as root.
2. Answer the question "Which port do you connect the laptop to, A or B?"
3. Type one of these commands, depending on the answer to Step 2:
Port A: eeprom ttya-ignore-cd=true
Port B: eeprom ttyb-ignore-cd=true
4. Shut down the 420R cleanly and reboot.
Now Solaris will be able to boot even when nothing is connected
to the console serial port.
-Greg
--
+++++ Greg Andrews +++ ge...@panix.com +++++
I have a map of the United States that's actual size
-- Steven Wright