strangeness with daemondo?

Wed Oct 29 02:15:54 PDT 2014

For me, it only associates with the first server and seems to ignore the rest if I start it using “sudo port load ntp”. Starting it with the same parameters as in the plist (/Library/LaunchDaemons/org.macports.ntp.plist), the ntpd daemon runs just fine and associates with all servers.

-- 
Andreas Kusalananda Kähäri
System Developer at BILS
Uppsala University, Sweden

> On 28 Oct 2014, at 20:05, Daniel J. Luke <dluke at geeklair.net> wrote:
> 
> I just updated the ntp port and am seeing some strange behavior (on Yostemite, I haven't tested it anywhere else yet):
> 
> If I create a launchd.plist for ntp that runs it directly, things work as expected. If I let Macports create one with the same ntpd command (but using daemondo), ntpd starts but doesn't associate with any peers.
> 
> Anyone else see anything like this, or have a thought as to what might be causing it?
> --
> Daniel J. Luke                                                                   
> +========================================================+                        
> | *---------------- dluke at geeklair.net ----------------* |                          
> | *-------------- http://www.geeklair.net -------------* |                          
> +========================================================+                        
> |   Opinions expressed are mine and do not necessarily   |                          
> |          reflect the opinions of my employer.          |                          
> +========================================================+
> 
> 
> 
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev