On Tue, Sep 01, 2015 at 09:21:03AM +0200, Peter Hessler wrote: > On 2015 Aug 31 (Mon) at 14:28:11 -0400 (-0400), Michael Reed wrote: > :On 08/31/15 07:36, Sebastian Benoit wrote: > :> Michael Reed([email protected]) on 2015.08.30 14:58:35 -0400: > :>> Hi all, > :>> > :>> If ntpd is run with the -n flag, and /etc/ntpd.conf is parsed without > :>> error, then "Configuration OK" is printed. I don't think this is > :>> particularly useful, as both a lack of an error message and an exit > :>> value of 0 already indicate success in this case. This seems to be the > :>> case for most (many?) programs in the base system, such as doas(1). > :> > :> I like the message. Why is it a problem? > :> > :> /Benno > :> > : > :It's admittedly not much of a problem, more just to follow the Unix > :principle of saying nothing if there's nothing wrong. > : > :Regards, > :Michael > : > > In my mind, -n is explicitly asking for a configuration check, so > explicitly telling me it's OK is a good thing.
sure, and if anyone wants less bother, just redirect the stderr like $ ntpd -n -f /etc/ntpd.conf 2>/dev/null ; echo $? 0 //gsoares
