lkml.org 
[lkml]   [1996]   [Mar]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: init und Linux 1.3.69
Date
In linux.dev.kernel, greg@wind.rmcc.com (G.W. Wettstein) wrote:
> On Mar 6, 8:52pm, Miquel van Smoorenburg wrote:
>
> The most common problem with syslog messages stalling is the inability
> of syslogd to resolve a hostname into an IP address when forwarding of
> remote messages is in effect. Even with the needed IP address
> definitions in /etc/hosts the library resolver code takes a fair
> amount of time to timeout if named is not running locally or if a
> remote named is down or inaccessible.
>
There's a reason for this, IMHO, and it's called "Stream socket".

Linux does have working Unix-domain datagram sockets now.

I would like to suggest that we switch back, or support both. It's not
difficult; after all, the code should still be in syslogd and in libc,
right? Just create a /dev/log_d as a datagram socket. syslog could fallback
to a connect to /dev/log if /dev/log_d is unavailable.

--
Being a _man_ means knowing that one has a choice not to act like a 'man'.
--
Matthias Urlichs


\
 
 \ /
  Last update: 2005-03-22 13:36    [W:0.097 / U:0.452 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site