"H"

hang console

Cause

Console hangs - but all other operations are working, including rlogin(1) and telnet(1). Rebooting the system (via a remote shell) clears the problem.

This problem occurs if another window is opened with the -C option, causing the console to hang. The other window could be another cmdtool window, shelltool window, or even an xterm window. Only one console window can be active at a time.

Action

The window/process that is causing the problem can be located by using the ps(1) command (auxw options may be necessary). The process can then be killed. Eliminate the console window running with -C, and control returns to the 'real' console.

Machine hung in reboot process: when the user is booting the machine, it hangs at checking filesystems.

A possible workaround is: 1. Boot miniroot from tape or CD-ROM, 2. mkdir mnt, 3. Mount the root partition to some mountpoint, i.e. /mnt, 4. Change directory to /mnt/dev, 5. Check to see if the console is located in the, 6. mnt/dev directory, 7. If not, make the device std.: MAKEDEV std, 8. Halt the system and reboot.

/home/string: No such file or directory

Cause

An attempt was made to change to a user's home directory, but either that user does not exist or the user's fileserver has not shared (exported) that filesystem.

Action

To check on the existence of a particular user, run the ypmatch(1) or nismatch(1) command, specifying the user name and then the passwd(4) map.

To export filesystems from the remote fileserver, become superuser on that system and run the share(1M) command with the appropriate options. If that system is sharing (exporting) filesystems for the first time, also invoke /etc/init.d/nfs.server start to begin NFS service.

See Also

For more information on sharing filesystems, see the share_nfs(1M) man page.

Host is down

Cause

A transport connection failed because the destination host was down. For example, mail delivery was attempted over several days, but the destination machine was not available during any of these attempts.

Action

Report this error to the system administrator for the host. If you are the person responsible for this system, check to see if the machine needs repair or rebooting.

Technical Notes

This error results from status information delivered by the underlying communication interface. If there is no known connection to the host, a different message usually results. See "No route to host" for details.

The symbolic name for this error is EHOSTDOWN, errno=147.

host name configuration error

Cause

This is an old sendmail(1M) message, which replaced "I refuse to talk to myself" and is now replaced by the "Local configuration error" message.

Action

See the message "554 string... Local configuration error" for details.

hosts.org_dir: NIS+ servers unreachable

Cause

This is the third of three messages that an NIS+ client prints when it cannot locate an NIS+ server on the network.

Action

If other NIS+ clients are behaving normally, check the Ethernet cabling on the workstation showing this message. On SPARC machines, disconnected network cabling also produces a series of "no carrier" messages. On x86 machines, the NIS+ messages might be your only indication that network cabling is disconnected.

If many NIS+ clients on the network are giving this message, go to the NIS+ server in question and reboot or repair it, as necessary. When the server machine is back in operation, NIS+ clients will give an "NIS server for domain OK" message.