Red Hat NETSCAPE MANAGEMENT SYSTEM 6.2 - COMMAND-LINE Guida di Installazione Scaricare il pdf (Pagina 17)

/etc/xinetd.d/rlogin: disable = no

/etc/xinetd.d/rsh: disable = no

/etc/xinetd.d/telnet: disable = no

/etc/xinetd.d/wu−ftpd: disable = no

At this point, the above output should raise some red flags. In the overwhelming majority of systems, all the

above can be disabled without any adverse impact. Not sure? Try it without that service. After disabling

unnecessary services, then restart xinetd:

# /etc/rc.d/init.d/xinetd restart

3.3.4. When All Else Fails

OK, if you can't find the "right" way to stop a service, or maybe a service is being started and you can't find

how or where, you can "kill" the process. To do this, you will need to know the PID (Process I.D.). This can

be found with ps, top, fuser or other system utilities. For top and ps, this will be the number in the first

column. See the Port and Process Owner section in the Appendix for examples.

Example (as root):

# kill 1163

Then run top or ps again to verify that the process is gone. If not, then:

# kill −KILL 1163

Note the second "KILL" in there. This must be done either by the user who owns the process, or root. Now

go find where and how this process got started ;−)

The /proc filesystem can also be used to find out more information about each process. Armed with the

PID, we can find the path to a mysterious process:

$ /bin/ps ax|grep tcpgate

921 ? S 0:00 tcpgate

# ls −l /proc/921/exe

lrwxrwxrwx 1 root root 0 July 21 12:11 /proc/921/exe −> /usr/local/bin/tcpgate

Security Quick−Start HOWTO for Red Hat Linux

3.3.4. When All Else Fails 14

1 2 ... 12 13 14 15 16 17 18 19 20 21 22 ... 81 82

Nessun commento

Red Hat NETSCAPE MANAGEMENT SYSTEM 6.2 - COMMAND-LINE Guida di Installazione Pagina 17