This could be any number of things. I know I see these kinds of messages
when certain Windows telnet clients log off. Of course, I also saw these
error messages back before I updated to the latest inetd in up2date.
You might also double check the max number of instances in inetd.conf. I
have a situation where users execute commands remotely on my linux
server through rcp and rsh, and with the default of 40 instances / 60
seconds was causing my users to be rejected with these messages in the
logs. I ended up increasing the max to 400, and that, combined with the
eratta updates fixed my problems. The inetd man page explains the max
instances pretty well.
So, basically, it depends on what process is running that is generating
these exit statuses. It could be nothing to worry about, or it could be
a really nasty problem.
HTH,
Wayne
Nathalie Boulos wrote:
>
> Hi again,
>
> I have the following lines in /var/log/messages
>
> ... inetd[26154] : pid 31019 : exit status 1
> ... inetd[26154] : pid 31020 : exit status 1
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
