Shulou(Shulou.com)06/01 Report--

This article will explain in detail how to start rpc.rstatd monitoring in the Linux system. The editor thinks it is very practical, so I share it with you as a reference. I hope you can get something after reading this article.

1 preparation work

You can verify that the rstatd daemon is configured on the server in two ways:

① uses the rup command, which is used to report various statistics for the computer, including configuration information for rstatd. Use the command rup 10.130.61.203, where 10.130.61.203 is the Ip of the linux/Unix server to be monitored, if the command returns relevant statistics. The rstatd daemon is configured and activated; if no meaningful statistics are returned, or an error report occurs, the rstatd daemon has not been configured or has a problem.

② uses the find command

# find /-name rpc.rstatd, this command is used to find out if the rpc.rstatd file exists on the system, and if not, the system does not have the rstatd daemon installed. You can refer to the Linux system to install rpc.rstatd services.

After downloading, start the installation. The installation steps are as follows:

Tar-xzvf rpc.rstatd-4.0.1.tar.gz

Cd rpc.rstatd-4.0.1/

. / configure-configure operation

Make-compile

Make install-start installation

Rpc.rstatd-start the rstatd process

2) configure the rstatd target daemon xinetd after installation. Its main configuration file is / etc/xinetd.conf, which contains the following basic information:

#

# xinetd.conf

#

# Copyright (c) 1998-2001 SUSE GmbH Nuernberg, Germany.

# Copyright (c) 2002 SuSE Linux AG, Nuernberg, Germany.

#

Defaults

{

Log_type = FILE / var/log/xinetd.log

Log_on_success = HOST EXIT DURATION

Log_on_failure = HOST ATTEMPT

# only_from = localhost

Instances = 30

Cps = 50 10

#

# The specification of an interface is interesting, if we are on a firewall.

# For example, if you only want to provide services from an internal

# network interface, you may specify your internal interfaces IP-Address.

#

# interface = 127.0.0.1

}

Includedir / etc/xinetd.d

What we need to modify here is the three conf files rlogin and rsh,rexec under / etc/xinetd.d/. Change the disable = yes in these three files to disable = no (disabled is used to disable services in the default {}) or set # default: off to on, which means that the above three services are started by default when xinetd starts!

Note: when I am configuring, I do not have the item disable = yes, so I change # default: off to: default: on. After restart (cd / etc/init.d/. / xinetd restart), check through netstat-an | grep 514, and no return is returned. Then, I manually add disable = no to the last line of the three files, restart xinetd, and then use netstat-an | grep 514 to view it. I get the result of tcp 000.0.0.0xinetd 514 0.0.0.0xinetd * LISTEN, which indicates that the rsh server has been started.

As long as you make sure that there are rstatd and xinetd services in the processes on the Linux machine, you can use LR to monitor them.

This is the end of the article on "how to start rpc.rstatd monitoring in Linux system". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.