I have a host whose *.* log messages are logged to another machine. I have an
entry in syslogd.conf like:
If loghost is down, it seems as if any process which uses the syslog() system
call blocks on its network transmission to loghost.
I thought syslogd used UDP and did not bother with reliability (eg. a log entry
is sent just once and if it does not arrive, then tough)
Is there anything I can do so that the machine's process table will not fill up
with blocking in.popd's and so on? The machine was at load 68.00 last night as
a result of this.
4th year; Confuser Engineering University of Canberra AUSTRALIA
Microsoft Network is prohibited from redistributing this work in any form,
in whole or in part. Copyright, Ben Elliston, 1995. License to distribute
this post is available to Microsoft for US$1000. Posting without permission
constitutes an agreement to these terms.