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 +========================================================+ | *---------------- [email protected] ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
