more digging in required (thanks, Matt, your comments, and of those in #ubuntu-bugs helped a lot).
I am always amazed by the depth of my ignorance...
/etc/network/if-(up|down|post-down|pre-up).d scripts are the responsibility of each package: NTP, NTPdate, and others. These scripts are executed whenever the action (reflected in the directory name) is executed.
So, it is not a n-m issue here. I was wrong. Nor it is NTP (not sure), or upstart. Will have to figure out.
Anyway: a summary, so far:
1. as provided, ubuntu has the /etc/network/if-up.d/ntp script disabled. As a result, connections purely managed from n-m do not get ntp service (so it seems). Why?
2. Although not hurting, ntp and ntpdate got installed; ntpdate cannot run if ntpd is running, so having both in *may* not be necessary.
more digging in required (thanks, Matt, your comments, and of those in #ubuntu-bugs helped a lot).
I am always amazed by the depth of my ignorance...
/etc/network/ if-(up| down|post- down|pre- up).d scripts are the responsibility of each package: NTP, NTPdate, and others. These scripts are executed whenever the action (reflected in the directory name) is executed.
So, it is not a n-m issue here. I was wrong. Nor it is NTP (not sure), or upstart. Will have to figure out.
Anyway: a summary, so far:
1. as provided, ubuntu has the /etc/network/ if-up.d/ ntp script disabled. As a result, connections purely managed from n-m do not get ntp service (so it seems). Why?
2. Although not hurting, ntp and ntpdate got installed; ntpdate cannot run if ntpd is running, so having both in *may* not be necessary.