string
string
string
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
statd: cannot talk to statd at <strong>string</strong><br />
Cause<br />
This message comes from the NFS status monitor daemon statd(1M), which<br />
provides crash recovery services for the NFS lock daemon lockd(1M). The message<br />
indicates that statd(1M) has left old references in the /var/statmon/sm and<br />
/var/statmon/sm.bak directories. After a user has removed or modified a host in<br />
the hosts database, statd(1M) might not properly purge files in these directories,<br />
which results in its trying to communicate with a nonexistent host.<br />
Action<br />
Remove the file named variable (where variable is the hostname) from both the<br />
/var/statmon/sm and /var/statmon/sm.bak directories. Then kill the statd<br />
daemon and restart it. If that doesn’t get rid of the message, kill and restart<br />
lockd(1M) as well. If that doesn’t work, reboot the machine at your convenience.<br />
stty: TCGETS: Operation not supported<br />
on socket<br />
Cause<br />
This message results when a user tries to remote copy with rcp(1) or remote shell<br />
with rsh(1) from one machine to another, but has an stty(1) command in the<br />
remote .cshrc file. This error results in failure of the rcp(1) or rsh(1) command.<br />
Action<br />
The solution is to move the invokation of the stty(1) command to the user’s<br />
.login (or equivalent) file. Alternatively, execute the stty(1) command in .cshrc<br />
only when the shell is interactive. Here is a test to do that:<br />
if ($?prompt) stty ...<br />
Alphabetical Message Listing 175
Change language