[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug-inetutils] Patch For Issue and Another Related Bug

From: Peter Rehley
Subject: [bug-inetutils] Patch For Issue and Another Related Bug
Date: Fri, 30 Jul 2004 23:25:27 -0700

Hi Tony,

> I assume moving the init() function until after the finet socket file
> descriptor has been created would correct this, but I have not taken
> this step due to the Law of Unforeseen Consequences. Frankly, I can live > with the syslogd start-up message being dropped if all the rest of them
> get logged on our log server. Maybe someone can look at the issue and
> roll a fix into the official version.

init(0) was moved from after finet to where it is now because the LogPort variable wasn't being set. This caused all messages from the internet to be lost. The problem with it after finet was that init(0) was being called after create_inet_socket. The init function sets the LogPort which is used by create_inet_sockets. The default value for LogPort is 0, which tells bind to pick some random port to use, but we need a known port for other processes to send messages to. That known port comes from getservbyname which looks in the services file.

See bug-inetutils message posted around Feb 10th, 2003

Hope this helps,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]