compilation bug fix for bsds
Yarin
yarin at warpmail.net
Wed Dec 29 18:04:55 EST 2010
OpenBSD.
Yes, I saw that, you have FreeBSD logging to the alert level but everything else to the info level.
If you do decide to add that to the FAQ then, I personally don't know about FreeBSDs default logging configuration, but please mention that both OpenBSD and NetBSD write daemon.info logs without problem. :-)
Yarin
----- Original message -----
From: "Sam Trenholme" <strenholme.usenet at gmail.com>
To: list at maradns.org
Date: Wed, 29 Dec 2010 10:35:30 -0700
Subject: Re: compilation bug fix for bsds
Sounds good. If I ever get time, I know that the Duende code has
special FreeBSD-only code to log its messages with FreeBSD's default
syslog.conf; maybe I could do the same here. As an aside, which
particular BSD are you using? FreeBSD? OpenBSD? DragonflyBSD?
NetBSD? (Whatever happened to NetBSD being the most portable
open-source *NIX clone out there?)
I won't be able to do this until next week.
- Sam
2010/12/28 Yarin <yarin at warpmail.net>:
> An FAQ entry would work.
>
> Thanks
>
> ----- Original message -----
> From: "Sam Trenholme" <strenholme.usenet at gmail.com>
> To: list at maradns.org
> Date: Tue, 28 Dec 2010 10:10:07 -0700
> Subject: Re: compilation bug fix for bsds
>
>> Open ./server/udpsuccess.c, and prepend the same 2 lines before all code (but not comments).
>
> Unless I can get a proper patch--and by "proper" I mean appropriate
> #ifdef statements so there is no chance the patch causes problems for
> people not using BSD--the best way to handle this issue is for me to
> add an appropriate entry to the MaraDNS FAQ.
>
> - Sam
>
>
More information about the list
mailing list