[Solved] Can't get into single user mode - sulogin was disabled

Solaris 10
trying to patch and therefore want to do this from single user mode

I do a

init 0

get's me to ok> :slight_smile:

ok> boot -s

I was a UK Sun Field Engineer for 10 years ..... I've used "boot -s " quite a bit .....

I get a console login , which I subsequently login into

#who -r 

returns run-level 3

?

can I force single user mode ?

Martin

init s
# or
shutdown -i s -g 0 -y

all should work just fine. init 0 is power off

No it isn't, init 5 is power off. init 0 drops you back to the OBP

will try the shutdown

cheers

You are correct.

?

init 5  

( five ) is poweroff, physically powers the box off.

init s 

or S is singleuser (though different apparently)

Jim said

init 0

is poweroff which it isn't.

init 0

takes you from a running OS to the OBP.

You're splitting hairs. init 0 is as close to powering off as you could get without "powering off".

Jim's point is that you should use init s not init 0.

what would you expect a

who -r

to return once booted into single user ?

I'd expect an s or maybe 1 , definitely not 3

---------- Post updated at 11:05 AM ---------- Previous update was at 10:58 AM ----------

Thats not splitting hairs at all. init 5 physically powers the box off. init 0 drops you back to the OBP from where you can then boot to any desired state. 2 totally different outcomes.

However, this isn't my concern.

I'm interested in Singleuser not OBP.
Why do I get runlevel 3 not S or 1 when I try and

boot -s

or

shutdown -i s -g 0 -y 

as I've just done..... this has actually fully booted the system back in multiuser mode.
Is there a way of disabling booting to singleuser? inittab?

I meant in terms of not being where you wanted to be. Indeed the difference is huge if it could mean paying a visit to a machine room. My bad.

Very strange. All of those things should have taken you to single user mode. I will try to recreate this scenario.

But no-one has said you should use init 5...

This is weird.
just tried dropping to the OBP with init 0

then gone for

ok> boot -m milestone=single-user

I've now got a constantly scrolling console that says something like
Requesting System Maintenance mode
Console Login Services () cannot run
svc.startd: could not exec() sulogin: No such file or directory

---------- Post updated at 12:03 PM ---------- Previous update was at 12:01 PM ----------

Is that helpful? Jim said init 0 was power the box off (which it isn't) I was merely correcting him saying init 5 is power the box off. It's got nothing to do with my issue.

About as helpful as arguing the toss about something no-one has actually advised you to do...

tbh we'd sort of moved on from that and it was you that brought it back up.
But thanks for your valuable input anyway, much appreciated.

What do you know about the constant loop trying to get to single-user mode?

Indeed. I (not quickly enough) removed the post you replied to. I wrongly thought you were misreading "init s" as "init 5".

no problem fella :wink:

---------- Post updated at 02:13 PM ---------- Previous update was at 12:16 PM ----------

Looks like sulogin has been disabled.... I've enabled it ;0)

Many thanks for the help.

1 Like