solaris 10 milestone startup problem
jlm3...@gmail.com
the system now wont complete the booting process until I enter root
password
Booting to milestone "svc:/milestone/multi-user:default".
dump on /dev/dsk/c0t0d0s1 size 4097 MB
Hostname: test
pseudo-device: zfs0
zfs0 is /pseudo/zfs@0
pseudo-device: devinfo0
devinfo0 is /pseudo/devinfo@0
pseudo-device: pm0
pm0 is /pseudo/pm@0
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Root password for system maintenance (control-d to bypass): /dev/rdsk/
c0t0d0s3 is clean
pseudo-device: dtrace0
dtrace0 is /pseudo/dtrace@0
sc>
sc> console -f
Enter #. to return to ALOM.
Login incorrect
Root password for system maintenance (control-d to bypass):
I then enter password and all is well
Entering System Maintenance Mode
Sourcing //.profile-EIS.....
root@test # who -r
. run-level 2 Feb 26 11:25 2 0 S
any ideas on how to correct this.
I'm running a t1000 on a trial and don't understand all the changes
introduced since 2.7
tim....@gmail.com
The console login service only runs in the the default milestone...
all
When Console login fails maintenance mode is requested and sulogin
called.
The heart of this issue is that if you do a dependency check of the
console login service, it has NO dependencies
Service that have no dependencies only start at milestone "all"
You can't restart the console login service because it can not co-
exist with sulogin, if you attempt to start the console login service
it will be in the offline state you should then be able to pkill
sulogin and the console login service will move to the online state.
This is the way smf works with the console login service, every
version of Solaris 10.
tim....@gmail.com
Oh... I should add... bot to milestone all
# svcadm milestone all
ThanksButNo
It occurs to me that running "svcs -x" might be a good idea,
in case there is some problem preventing it from working the
way it should.
/:-/