Solaris 7 5/99 Release Notes (SPARC Platform Edition)

System Administration Bugs

init Does Not Recognize Carrier Drop Off From a Serial Display and Therefore Does Not Revert to the Default Console (4191023)

If you lose the carrier, i.e., become disconnected from the serial port (that is not located on the default console or on an auxiliary console through which you are logged in, and then bring the system to single-user or administrative mode by executing the init command from that port, you must ensure that the carrier is reestablished on that serial port before bringing the system back up. The system then prompts you for a run level to which you want to boot the system (only on the port where the init command was initiated).

Workaround: Reconnect to the serial ports when you lose the carrier before rebooting the system.

init Prompts for Run Level When the reboot Command Is Executed From a Standalone Session (4191148)

A misleading message is sometimes displayed on the device on which you initiated the init state transition when administering a system using the init command even though you executed the reboot command. When executing init s, a single-user shell is established on a remote console and the subsequent rebooting of the system can cause the following message to be displayed:

Enter run level

Workaround: Ignore the misleading message.

Change the init Command's Run Level Prompt to Display on a tty On Which Shift D or the exit Command Are Executed (4196862)

If you press Shift--D as a superuser or after logging in as root from the superuser login prompt and then issue an exit command to be at the default run level, you are prompted for the default run level. The prompt is displayed on a console on which the init command was initially executed instead of the console on which Shift--D or the exit command were originally issued.

If you execute the init command from a pty, /dev/console becomes the default device on which you are prompted for a run level. If you are running a remote console and log in as a superuser and then type Shift--D to boot the system, the run level prompt is then displayed on the console instead of the auxiliary console.

The init Command Does Not Display Its Run Level Prompt When Reconnecting to the Port of an Auxiliary Console (4196993)

If a configuration includes one or more auxiliary consoles and the carrier drops the connection for the auxiliary console on which the init command was run, and the sulogin shell has exited from another auxiliary or default console, then the following prompt will not be displayed after reestablishing the connection on the port from which the carrier dropped the connection:


Although you are never prompted for the run level, the system is still waiting for the run level to be entered.

Workaround: Reestablish the connection on the port from the carrier has dropped the connection and enter the desired run level even though you are not prompted for the run level.

Some Console Messages Cannot Be Redirected to Auxiliary Consoles (4197589)

Daemons or commands may use /dev/console explicitly to display messages. The frequency of such messages is low among the set of messages that the console may display.

Workaround: All messages are still printed to /dev/console and can therefore be monitored. You can also monitor syslog log files.

syslog Writes Messages to /dev/syscon When Unable to Send to syslogd (4219265)

If syslogd needs to display error messages on a console, these messages will be directed to the default location /dev/syscon. The error messages are not displayed on any configured auxiliary consoles in this feature patch.

UFS Quotas Not Enabled After Booting (4226352)

If you have UFS file systems listed in /etc/vfstab with quotas enabled, you must apply the following workaround. Otherwise, quotas are not enabled automatically after booting a system.

Workaround: You must run quotacheck -a and quotaon -a for quotas to be correctly enabled. Otherwise, quotas remain disabled.