Thanks! I'll try the fix mentioned.

Cheers,
Anders

--
This mail was sent on Sun 05/29/05 at 5:29AM PDT


There is a multi-legged creature crawling on your shoulder.
=09=09-- Spock, "A Taste of Armageddon", stardate 3193.9

*************************************************************************
* Anders Hogrelius       Cell :  +46(0)70 884-2775, +46(0)70 677-0210
* Tessingatan 12         Phone:  +46(0)8 501-64524, +1(714)408-7868
* SE-72216 Vasteras      E-mail: anders@hogrelius.nu
* SWEDEN=09=09 Web:    http://www.hogrelius.nu/~ahs/

On Sun, 29 May 2005, Havard Eidnes wrote:

> > My server seems to have developed a weird problem in the last couple of
> > days. It's a PC164 running NetBSD 1.6.1 and the problem is that syslogd
> > dies without any obious reason. I noticed the problem because newsyslog
> > reports that there is no pid for syslogd and has done so the last cpl o=
f
> > days.
> >
> > Is there anyone aware of any new exploits that could trigger this?
>
> Yes, I think I know what this is.  This problem (or at least one
> quite similar to it) was reported in PR#24682, "syslogd may die
> if HUP arrives in a certain phase of DNS lookup".
>
> The fix for this problem was committed on the trunk in revisions
> 1.64 and 1.65, and was subsequently pulled up to the netbsd-1-6
> branch in revision 1.51.2.2 of usr.sbin/syslogd/syslogd.c.
>
> >From the looks of it, that revision has not (yet) been published
> as part of any official binary release in the netbsd-1-6 series,
> so you'll have to do a source update along netbsd-1-6 for syslogd
> to pick up the fix.
>
> Regards,
>
> - H=E5vard
>