hUnTeR wrote:
> Thanks, i REALLY appreciate the thoughts and the response. Your latter
> suggestion makes 100% sense to me, and i hadnt thought of that.
But, does it work? ;)
> As for
> the looping errors, i do see them on occasion on /dev/tty8 which is
> where i pipe all the syslog stuff to.
If you get messages about looping, then too many connections (more than
40 in a sixty second period) are being made to the service that inetd is
shutting down. You can change the number of connections that inetd will
accept for a particular service by changing the "(no)wait" section to
"(no)wait.100", for instance. The appended number becomes the number of
connections allowed.
> As for /var/log/messages here are
> a few:
>
> Nov 24 17:54:30 ns1 inetd[16835]: getpwnam: root: No such user
> Nov 24 17:54:46 ns1 inetd[262]: ftp/tcp: unknown service
...
> Nov 24 17:54:46 ns1 inetd[262]: linuxconf/tcp: unknown service
Do you REALLY provide all of those services? I'd recommend turning some
of them off (especially linuxconf).
> And so on, when i try killall -HUP inetd
Perhaps you should update to the latest inetd, too? It acts like it's
not rewinding the FILE's.
MSG
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
