compilation bug fix for bsds

[Yarin]

It looks like you make the man pages and such from the .ej files, so I have a patch for the duende.ej file, adding documentation for the --pid option in the first chunk and mentioning the BSD logging in the second chunk.

In case the formatting isn't preserved here, it's also attached.


--- ./doc/en/source/duende.ej	2008-09-09 06:40:20.000000000 -0500
+++ ./doc/en/source/duende.ej	2010-12-29 21:07:03.605883241 -0600
@@ -14,14 +14,17 @@
 LOG_INFO.
 
 <H1>USAGE</H1>
-<b>duende</b> child_process [ all subsequent arguments passed on to child ]
+<b>duende</b> (--pid=/path/to/file) child_process [ all subsequent arguments passed on to child ]
 
 <H1>DETAILS</H1>
 
 When <b>duende</b> is invoked, it spawns two processes.  In addition to
 spawning the daemonized child process, <b>duende</b> also spawns a process
 which reads and logs the standard output of the daemonized process.  The
-parent process stays alive so as to monitor the daemonized process.
+parent process stays alive so as to monitor the daemonized process. If
+the optional <tt>--pid</tt> argument is supplied, <b>duende</b> will write
+it's PID to the file specified by the argument. It is an error to supply
+the <tt>--pid</tt> argument without an equal sign and file name.
 <p>
 <b>duende</b> requires a blank directory named <tt>/etc/maradns/logger</tt> 
 to run.
@@ -52,10 +55,11 @@
 to <b>duende</b>.  All messages created by the child process are sent
 to syslog() with a priority of LOG_INFO and a "facility"
 of LOG_DAEMON (daemon.info in /etc/syslog.conf); since daemon.info
-messages are not logged by default in FreeBSD, on FreeBSD systems
-messages generated by the child process are logged with a priority of
-LOG_ALERT and a "facility" of LOG_DAEMON (daemon.alert in /etc/syslog.conf).
-Should duende itself encounter an error, it will send
+messages are not logged by default in FreeBSD, on and only on FreeBSD
+systems, messages generated by the child process are logged with a priority
+of LOG_ALERT and a "facility" of LOG_DAEMON (daemon.alert in
+/etc/syslog.conf). OpenBSD and NetBSD known to log properly with the
+default level. Should duende itself encounter an error, it will send
 messages to syslog() with a priority of LOG_ALERT.  <p>
 
 For example, suppose one invokes duende thusly:


released under the two-clause BSD license

----- Original message -----
From: "Yarin" <yarin at warpmail.net>
To: list at maradns.org
Date: Wed, 29 Dec 2010 17:04:55 -0600
Subject: Re: compilation bug fix for bsds

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
>
>