18.02.2014 Views

string

string

string

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

group.org_dir: NIS+ servers<br />

unreachable<br />

Cause<br />

This is the second of three messages that an NIS+ client prints when it cannot locate<br />

an NIS+ server on the network.<br />

Action<br />

See the message "hosts.org_dir: NIS+ servers unreachable" for details.<br />

"H"<br />

hang console<br />

Cause<br />

Console hangs - but all other operations are working, including rlogin(1) and<br />

telnet(1). Rebooting the system (via a remote shell) clears the problem.<br />

This problem occurs if another window is opened with the -C option, causing the<br />

console to hang. The other window could be another cmdtool window, shelltool<br />

window, or even an xterm window. Only one console window can be active at a<br />

time.<br />

Action<br />

The window/process that is causing the problem can be located by using the ps(1)<br />

command (auxw options may be necessary). The process can then be killed. Eliminate<br />

the console window running with -C, and control returns to the ’real’ console.<br />

Machine hung in reboot process: when the user is booting the machine, it hangs at<br />

checking filesystems.<br />

A possible workaround is: 1. Boot miniroot from tape or CD-ROM, 2. mkdir mnt, 3.<br />

Mount the root partition to some mountpoint, i.e. /mnt, 4. Change directory to<br />

/mnt/dev, 5. Check to see if the console is located in the, 6. mnt/dev directory, 7. If<br />

not, make the device std.: MAKEDEV std, 8. Halt the system and reboot.<br />

Alphabetical Message Listing 77

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!