On 9/13/07, Jon Nettleton <jon.nettleton(a)gmail.com> wrote:
I tentatively have a working config. I added N as another runlevel
that chkconfig can turn on and off. The problem is that the scripts
are slightly different for NMDispatcher than standard init. I am
starting to lean more towards having another tab in
system-config-services that manages them like xinetd. I am open to
exposing NMDispatcher controlled services like xinetd is handled now
is probably fine.
Here's the next question.
How do you add more services to NMDispatcher's control? From a
packager's perspective what do I have to do to ship a package with a
network based service script? Am I going to have to ship two different
versions of the script? One for the legacy network system and another
for the NMDispatcher?