> I could do that (I agree that it is a better name). I vaguely remember > Meem mentioning to me a existing practice for naming daemons that > command line tools interact with, which was you add a "d" to the name of > the command to get the daemon. (Meem, if I didn't remember that > correctly, let me know and we'll use Seb's suggested name).
It's correct (e.g. sysevent/syseventd and automount/automountd). But as Jim pointed out, our service needn't have the same name as the daemon itself. That said, I'm not too wild about "network/link-management", as both "link" and "management" are pretty nebulous. However, I can't really think of anything better offhand :-( -- meem
