Trusted Solaris Administrator's Procedures

To Prevent Logins From Being Disabled After a Reboot

In the Trusted Solaris environment, the /etc/nologin file is created after boot and is not removed until a user with the Enable Logins authorization enables logins.

If your site's security policy allows, the Security Administrator role can edit the RMTMPFILES script in /etc/init.d to comment out the lines that recreate the /etc/nologin file. See "To Prevent Logins From Being Disabled After a Reboot", if changing the default is consistent with your site's security policy.

  1. Assume the Security Administrator role and go to an ADMIN_LOW workspace.

  2. Use the Admin Editor action to open the /etc/init.d/RMTMPFILES for editing.

    See "To Edit a Local File", if needed.


    Note -

    Do not create a backup file in the /etc/init.d directory. Because all files in the startup directories are executed, the backup file would be executed after the changed version, so the /etc/nologin file would be re-created, and the effect of this procedure would be undone.


  3. Comment out the lines that disable logins after a reboot.

    Comment out the active lines as shown in the following screen.


    # cp /dev/null /etc/nologin
    # echo "" >> /etc/nologin
    # echo "NO LOGINS: System booted" >> /etc/nologin
    # echo "Logins must be enable by an authorized user." >>
    # /etc/nologin
    # echo "" >> /etc/nologin
  4. Save and quit the file.


    :wq