> > This patch adds service registration and unregistration and enginge 
> > addition and removal to slon for win32.
> 
> Thanks, patch applied.
> 
> I think there is an enhancement that should be made however - 
> at present, when you install the service it actually installs 
> in a state in which it won't start because no engines have 
> been registered. Perhaps it should install in 'Disabled' 
> startup mode, which is then set to 'Automatic' when the first 
> engine is registered. When removing the last engine, it can 
> be set back to 'Disabled'.

I don't like this at all. Once we have installed, we should not modify
the service configuration because what we do may conflict with something
the user did manually. (Say he set it to Manual, then he registers a new
engine, and pop it's in automatic again. Personally I absolutely hate
tools that do that..)


> Otherwise, on reboot the (potentially scary!) 'A service or 
> device driver failed at startup - see the system event log 
> for details' error will likely be displayed.
> 
> Thoughts?

I see the problem. Another solution to this would be to have Slon start
up (and not crash!) and just log a warning in the eventlog if it has no
configured engines? Because something *is* wrong, but we'd show it in a
less scary fashion... Reasonable?

Or possibly just start up and not even log, just standing by for
somebody to do something...

//Magnus