NT Service Control Manager - was Re: Samba under Coherant and Macintosh

[John E. Malmberg]

Luke Kenneth Casson Leighton <lkcl#samba.org> wrote:


>> While a utility to emulate the WINDOWS NT Service manager may have a lot
of
>> uses, I do not see a strong need for it.  I would also want to greatly
>> restrict what it was allowed to do by an independant means than the main
>> init.d file.
>
>the plan would be that you would have to provide your own scripts, with a
>start and stop option.


Actually that does become an issue, as the first thing that the NT GUI
service control manager is inquire each service as what commands it supports
of the set Start, Stop, Pause, Continue.

The start command can also pass optional parameters also.

If it does not respond, and the process is running then a status of "not
responding" or equivalent is returned for a zombie process.

One of the uses of this is on NT to see if a service has become a zombie.

So the script for the service would need to also be able to return this
information, unless you fake it, and thus cripple the end functionality.

Are you planning a full implementation for those services that can support
it?  Or just restrict it to the Start and Stop functions, and assume if the
process exists that it is not in a zombie state.


>of course, kill -TERM only works as root or as the user that started a
>service, therefore you cannot just terminate services as an anonymous
>user.


As long as you have  proper mapping of the remote user name to the local
username.

Obviously most of this has been solved.  The issue seems to be on how to
best keep track of multiple connections and sessions, as per the other
discussions.  The platform I am using will not support a lot of short lived
spawned processes.

-John
wb8tyw at qsl.network