On 23 Jul 2002, Keith Winston wrote:
On Tue, 2002-07-23 at 00:10, Rick Green wrote:
I've just noticed a few 'anomalies' with a SuSE 8 system I just set up and put into production. Can anyone explain why:
..I get a 'syslogd 1.4.1: restart.' message at :15 past every hour?
...I can't seem to disable portmap? Yast2 insists on enabling it in whatever runlevel I have inetd starting. All I'm running out of inetd is ftp, time, and pop3, and to my knowledge, none of them require portmap. So why can't I disable this reputedly-insecure service?
Portmap will be started if you have the NFS server or client enabled. Check that in the run level editor. The service names are "nfs" and "nfsserver".
neither of those are running. Here's the current status: :~> netstat -l Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 *:time *:* LISTEN tcp 0 0 *:pop3 *:* LISTEN tcp 0 0 *:sunrpc *:* LISTEN tcp 0 0 *:www-http *:* LISTEN tcp 0 0 *:ftp *:* LISTEN tcp 0 0 *:smtp *:* LISTEN tcp 0 0 localhost:x11 *:* LISTEN tcp 0 0 *:ssh *:* LISTEN tcp 0 0 localhost:x11 *:* LISTEN udp 0 0 *:time *:* udp 0 0 *:sunrpc *:* I'd really like to turn off sunrpc (portmapper). I know I can just kill it, or manually edit the init scripts, but then yast2 will just undo my work the next time I use it for anything... RIck Green
Alle 20:56, martedì 23 luglio 2002, Rick Green ha scritto:
On 23 Jul 2002, Keith Winston wrote:
On Tue, 2002-07-23 at 00:10, Rick Green wrote:
I've just noticed a few 'anomalies' with a SuSE 8 system I just set up and put into production. Can anyone explain why:
..I get a 'syslogd 1.4.1: restart.' message at :15 past every hour?
...I can't seem to disable portmap? Yast2 insists on enabling it in whatever runlevel I have inetd starting. All I'm running out of inetd is ftp, time, and pop3, and to my knowledge, none of them require portmap. So why can't I disable this reputedly-insecure service?
Portmap will be started if you have the NFS server or client enabled. Check that in the run level editor. The service names are "nfs" and "nfsserver".
neither of those are running. Here's the current status: :~> netstat -l
Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 *:time *:* LISTEN tcp 0 0 *:pop3 *:* LISTEN tcp 0 0 *:sunrpc *:* LISTEN tcp 0 0 *:www-http *:* LISTEN tcp 0 0 *:ftp *:* LISTEN tcp 0 0 *:smtp *:* LISTEN tcp 0 0 localhost:x11 *:* LISTEN tcp 0 0 *:ssh *:* LISTEN tcp 0 0 localhost:x11 *:* LISTEN udp 0 0 *:time *:* udp 0 0 *:sunrpc *:*
I'd really like to turn off sunrpc (portmapper). I know I can just kill it, or manually edit the init scripts, but then yast2 will just undo my work the next time I use it for anything...
If you do not need it.... try to uninstall it. Praise
On Tuesday 23 July 2002 20.56, Rick Green wrote:
I'd really like to turn off sunrpc (portmapper). I know I can just kill it, or manually edit the init scripts, but then yast2 will just undo my work the next time I use it for anything...
rcportmap stop insserv -r portmap YaST2 will *not* turn it back on. At least it doesn't for me. Not without manually clicking somewhere portmap-related :) regards Anders
On Tue, 23 Jul 2002, Anders Johansson wrote:
rcportmap stop insserv -r portmap
YaST2 will *not* turn it back on. At least it doesn't for me. Not without manually clicking somewhere portmap-related :)
maybe this is another clue: :~ # rcportmap stop Shutting down RPC portmap daemon done :~ # insserv -r portmap insserv: Warning, current runlevel(s) of script `apache' overwrites defaults. insserv: Warning, current runlevel(s) of script `apcupsd' overwrites defaults. I'm not using the 'NIS' feature of apcupsd, so I don't think that's the culprit... Rick Green
On Tuesday 23 July 2002 21.41, Rick Green wrote:
On Tue, 23 Jul 2002, Anders Johansson wrote:
rcportmap stop insserv -r portmap
YaST2 will *not* turn it back on. At least it doesn't for me. Not without manually clicking somewhere portmap-related :)
maybe this is another clue: :~ # rcportmap stop
Shutting down RPC portmap daemon done
:~ # insserv -r portmap
insserv: Warning, current runlevel(s) of script `apache' overwrites defaults. insserv: Warning, current runlevel(s) of script `apcupsd' overwrites defaults.
I'm not using the 'NIS' feature of apcupsd, so I don't think that's the culprit...
Those messages aren't about portmap. When you use insserv it will check all scripts you have, and what those messages are saying, basically, is that you have start-links for those scripts in runlevels where they're not defined in the actual scripts. The default for apache, for instance, is runlevels 3 and 5. If you were to create a symlink for apache in runlevel 2 you'd see that message when you use insserv, but it does not mean that insserv didn't do what you told it. Hope that's at least slightly clearer than mud :) In any case, you should be seeing portmap starting at bootup any more after this. //Anders
participants (3)
-
Anders Johansson
-
Praise
-
Rick Green