On Thu, Mar 5, 2015 at 12:19 AM, Isaac Dunham <[email protected]> wrote: > On Wed, Mar 04, 2015 at 10:05:06PM +0000, Laszlo Papp wrote: >> Better, thanks, but the documentation would still not mention the case of >> abort. >> >> On Tuesday, March 3, 2015, Isaac Dunham <[email protected]> wrote: >> > How is this patch for clarifying the documentation? > >> > //usage: ) >> >+//usage: "\n If no peer is defined, ntpd will not run" >> > //usage: IF_FEATURE_NTPD_SERVER( >> >+//usage: "\n unless ntpd is running as a server (-l)" > <snip> > > Are you sure? > I didn't use the word "abort", but it seemed to me that "if no peer > is defined, ntpd will not run" should make the behavior clear.
The problem is not when no peer is defined. The problem is when the peer is defined, but we cannot talk to it. Therefore, the issue that I raised is still addressed with regards to this. > > Thanks, > Isaac Dunham _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
