Any way to supress xinetd on the System Log?



  • This is flodding the System Log, all over the place!

    Hapenning in all servers running 2.3 by the way.

    
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19055-udp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19055-tcp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19054-udp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19054-tcp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19053-udp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19053-tcp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19052-udp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19052-tcp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19051-udp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19051-tcp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19050-udp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19050-tcp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19049-udp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19049-tcp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19048-udp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19048-tcp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19047-udp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19047-tcp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19046-udp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19046-tcp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19045-udp
    May 27 16:27:03 	xinetd 	19245 	readjusting service 19045-tcp 
    
    


  • Come on… am I the only one with this issue?


  • Rebel Alliance Developer Netgate

    No easy way… would have to be shunted to some other log via syslog

    Or maybe in filter.inc around line 2387 where it's launched you can edit "-filelog /dev/null" into its parameters

    Or you can ditch NAT+Proxy reflection for pure NAT reflection and it'll stop xinetd entirely. :-)


  • Banned

    @LFCavalcanti:

    Come on… am I the only one with this issue?

    +1

    …lots of spam in the log recently. Hard to find anything useful.



  • I just send xinetd logging to ntp.log (tried to send it to his own log just in case, but couldn't). It's probably not a permanent solution, i guess syslog.conf file will be rewritten on reboot.

    Just change this two lines on /etc/syslog.conf and restart the syslogd service

    !ntp,ntpd,ntpdate,xinetd

    !-xinetd,ntp,ntpd,ntpdate,charon,ipsec_starter,openvpn,….