Am Thu, 28 Nov 2013 08:55:56 -0700 schrieb Christoph Junghans <ott...@gentoo.org>:
> 2013/11/28 Rich Freeman <ri...@gentoo.org>:
> > On Wed, Nov 27, 2013 at 10:56 PM, Paul B. Henson <hen...@acm.org>
> > wrote:
> >> On Fri, Nov 22, 2013 at 09:36:38PM +0100, Peter Stuge wrote:
> >>> Paul B. Henson wrote:
> >>> > In openntpd ebuilds starting with version 20080406-r3, logging
> >>> > was changed from using the default standard syslog to running
> >>> > the daemon in debug mode, logging to stderr, and having
> >>> > start_stop_daemon background the process itself and redirect
> >>> > the output to a log file.
> >>> >
> >>> > I think this is broken.
> >>>
> >>> Yes, I think it is really f-ing broken too.
> >>
> >> Well, looks like it's just you and me in that camp :(, quite
> >> disappointing no other devs stepped up with an opinion on this.
> >> Guess I'll just fix this in my local overlay and the rest of the
> >> users can fend for themselves.
> >
> > Did anybody actually talk to the maintainer about this and ask why
> > this was done? That would probably be a good first step if you want
> > it to change. Having 47 devs agree with you doesn't really
> > accomplish much if none of them care to maintain the package in
> > question.
> Paul talked to me via the bug tracker, bug 491134, and due to
> discussion we had there openntpd-20080406-r5 features a use flag to
> bring back syslog support (for details see the bug). This allows to
> run openntpd with two different ways of logging, via syslog (like Paul
> wants) and with a separate log file to avoid boot delays (like djc
> wants). We could easily make syslog logging the default, like
> polynomial-c suggested in another thread, but syslog is enabled in
> most profiles by default anyway.
>
> >
> > Also, you can always publish your overlay. :)
> >
> > Rich
> >
>
>
>
I think I messed something up here.
Yesterday I tried to reply on the latest mail being in this discussion
thread but added Christoph's email address with a typo so the reply was
not sent at all. I then only sent the reply to him and not to the list.
So for completeness, here's my reply from yesterday:
[Begin of quote]
CCing ottxor (he's our openntpd maintainer) so he won't miss further
discussion about this.
Actually I partially do agree with the complaints that appeared in this
thread.
If logging once was done via syslog this should not be changed.
So rather than making this available via USE flag being disabled
by default I'd rather prefer to have the USE flag being enabled by
default.
I do not agree with Paul's suggestion to remove the -d option from the
init script again. Unfortunately openntpd does not create a PIDfile
once it gets started. This would not be a problem if openrc would not
require a PIDfile to _reliably_ determine if the daemon is still
running or not. So I think ottxor did the only right thing here.
On the other hand since the daemon's init script starts the daemon with
-d I see occasional ntpd crashes on one of my systems. I'm still
investigating this and right now won't blame anyone.
Fixes for the boot delays have already been mentioned (don't use ntpd's
-s option) and other problems I cannot really see.
[End of quote]
I think there's some confusion on what the -d option actually does, so
let me cite the relevant parts from "man 8 ntpd":
ntpd uses the adjtime(2) system call to correct the local
system time without causing time jumps. Adjustments larger than
128ms are logged using syslog(3) with LOG_INFO priority. The
threshold value is chosen to avoid having local clock drift
thrash the log files. Should ntpd be started with the -d
option, all calls to adjtime(2) will be logged.
[snip]
-d Do not daemonize. If this option is specified, ntpd will
run in the foreground and log to stderr.
[snip]
-v This option allows ntpd to send DEBUG priority messages
to syslog.
Now let's discuss if this can be considered as "debug mode" or not.
@Christoph: Sorry I messed up your nickname so badly :-/
--
Lars Wendler
Gentoo package maintainer
signature.asc
Description: PGP signature
