[Wrapper-user] .bat equivalent of {start|stop|console|dump}

[<da...@ix...>]

The newer Wrapper binaries, with the -t|-p support to start|stop NT
services is great (actually solved a problem for us last night).

However, having to take a config file option is a bit of a nuissance.
Especially since we already have the config file set up in the .bat file.

So, has there been any thought given to enhancing the .bat file to allow
{start|stop|console} to work the same as it does with the Unix script?

Right now the Unix and NT scripts behave differently.  The Unix script only
takes a single action parameter, while the NT script only takes a single
configuration file parameter.

I'd really like to propose that they come closer to performing similarly.

I think it'd be fairly easy to enhance both to take 2 parameters, the first
being one of {start|stop|console} and the optional second being a config
file.

I'm not sure what to do about dump on the NT side.  Help?

Anyway, I know this would be a big change for the NT script side, but, do
many people actually use the feature of the .bat file taking a config file
as a parm?  Would such a change break many people?

What about if, for a while, on the NT side, if the first param is not one
of {start|stop|console|dump} that a warning is issued, and the param is
used as a config file.  Then some later release, the {start|stop|console}
becomes mandatory?

Internally I will probably be making these changes anyway, but if the
Wrapper community has any thoughts on an approach they would accept, I'd be
willing to design towards that end.

Cheers,
mrc
-- 
     Mike Castle      da...@ix...      www.netcom.com/~dalgoda/
    We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc