Description of problem: Historically, we just drop to a shell. Version-Release number of selected component (if applicable): event-compat-sysv-0.3.9-5.fc9
What problems are created by this?
Changed expectations. Just changing it to /bin/bash should work.
Just built 0.3.9-6 I'll test it further when I can be in the physical presence of my testing box.
Latest package behaves well. Closing this one
Ahem. Many sites have this in their /etc/inittab: sum:S:wait:/sbin/sulogin And to top it off, the comments at the top of /etc/event.d/rcS-sulogin say: # This task runs the sulogin binary during "single-user" mode. And the file is *called* 'sulogin', not rcS-runbash. I'd say there's an expectation that it invokes /sbin/sulogin, not a raw unprotected shell.... Possible work-around while /etc/inittab is still around: script runlevel --set S >/dev/null || true grep -q 'S:wait:/sbin/sulogin' /etc/inittab if [ $? = 0 ]; then /sbin/sulogin else /bin/bash fi if [ -r /etc/inittab ]; then
Don't think it's practical to rely on the presence of inittab. Renaming the file could be an option, though.
That being said, it still falls under the general category of 'if you have customized your /etc/inittab, you will need to do customization of the default upstart setup.'
Right - but there's 2 points here: (1) There's precious little doc yet on how to customize it, and (2) The file is *called* sulogin, the comment at the top *says* it runs sulogin - but it doesn't, it runs bash instead. Certainly counter-intuitive.