I'm fairly certain that illumos syslogd is udp based, and will proceed happily
(dropping log entries if appropriate) if it can't keep up. Some may consider
this a security concern… what is more important? Having log data showing that
the system is too busy to respond, or having a system that is responsive even
without log data? Reasonable people may disagree here…
-- Garrett
On Oct 7, 2012, at 8:17 PM, Joseph Anthony Pasquale Holsten
<[email protected]> wrote:
> Does syslog(3c) ever block under illumos? The nginx team refuses to even
> include it because glibc syslog(3) hangs if /dev/log gets full, eg if syslogd
> stops. This seems crazy to me, but apparently the glibc team considers it a
> security feature to never drop logs.
> --
> http://josephholsten.com
>
> -------------------------------------------
> illumos-discuss
> Archives: https://www.listbox.com/member/archive/182180/=now
> RSS Feed: https://www.listbox.com/member/archive/rss/182180/22003744-6133b79f
> Modify Your Subscription: https://www.listbox.com/member/?&;
> Powered by Listbox: http://www.listbox.com
-------------------------------------------
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be
Modify Your Subscription:
https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4
Powered by Listbox: http://www.listbox.com
