Why doesn svcs -x know why my /system/console-login is in the offline state?
If you boot to milestone none and from there go to milestone all (see question 3.5) without exiting the sulogin shell, svc.startd(1M) keeps console-login in the offline state. svcs -x sees that all of console-login’s dependencies are satisfied, and can’t figure out why console-login is offline. Your system is fine. svc.startd(1M) will notice when you’ve logged out of your sulogin shell and will start console-login properly after that. In another situation, if you have a file: dependency which was not satisfied when your service start, but the file is present when you run svcs -x, SMF reports that it can’t determine the reason why your service is offline. You should refresh your service (see question 3.9).
Related Questions
- IF THE SUBMITTED DIGITAL IMAGES DO NOT CONFORM TO THE SPECIFICATIONS, THE PROCEDURES STATE THAT THE SYSTEM WILL AUTOMATICALLY REJECT THE E-DV ENTRY FORM AND NOTIFY THE SENDER. DOES THIS MEAN I WILL BE ABLE RE-SUBMIT MY ENTRY?
- How will citizens and state agencies use the Mississippi Management and Reporting System (MMRS) to track stimulus-related expenditures?
- Why doesn svcs -x know why my /system/console-login is in the offline state?
