NIS stops responding for few minutes and back to normal again Post: 5129

3 More Discussions You Might Find Interesting

1. Solaris

Change hostname, NIS stops

All, I have changed my machine name from A202 to B205. All I modified was /etc/hosts, /etc/nodename, hostname.ce0, /etc/net/<stuff needed to change>. But for some reason now NIS does not work. This is not the NIS server. When I telnet in I get "No directory! Logging in with home=/" when I...

2. AIX

FTP daemon stops responding

I have a strange problem with the FTP server on AIX 5.2. During the busiest time of the day, we get intermittent connection failures or timeouts connecting to the ftp server. The only thing clue that I can find is that daemon log shows the following message: ftpd: /bin/ls: Resource temporarily...

3. Shell Programming and Scripting

How do I get my shell back to normal readline?

I just ran an application that crashed... but before it did, it managed to set readline echo off, and probably a bunch of other settings. Is there any way I can just tell my shell to re-initialize? To get back to whatever state existed before my shell got messed up by this evil program?

LEARN ABOUT CENTOS

rusers

RUSERS(1)						    BSD General Commands Manual 						 RUSERS(1)

NAME

     rusers -- who is logged in to machines on local network

SYNOPSIS

     rusers [-al] [host ...]

DESCRIPTION

     The rusers command produces output similar to who, but for the list of hosts or all machines on the local network. For each host responding
     to the rusers query, the hostname with the names of the users currently logged on is printed on each line. The rusers command will wait for
     one minute to catch late responders.

     The following options are available:

     -a      Print all machines responding even if no one is currently logged in.

     -l      Print a long format listing. This includes the user name, host name, tty that the user is logged in to, the date and time the user
	     logged in, the amount of time since the user typed on the keyboard, and the remote host they logged in from (if applicable).

DIAGNOSTICS

     rusers: RPC: Program not registered
	     The rpc.rusersd(8) daemon has not been started on the remote host.

     rusers: RPC: Timed out
	     A communication error occurred.  Either the network is excessively congested, or the rpc.rusersd(8) daemon has terminated on the
	     remote host.

     rusers: RPC: Port mapper failure - RPC: Timed out
	     The remote host is not running the portmapper (see portmap(8) ), and cannot accomodate any RPC-based services.  The host may be down.

SEE ALSO

     rwho(1) users(1), who(1), portmap(8), rpc.rusersd(8)

HISTORY

     The rusers command appeared in SunOS.

BUGS

     The sorting options are not implemented.

Linux NetKit (0.17)						  August 15, 1999					       Linux NetKit (0.17)