Re: [Wrapper-user] Config File Naming

[Jim R. <jr...@er...>]

Leif,

Before I did through the code, does this "also" mean that you have made 
the changes as proposed so that the wrapper configuration file name 
follows the executable name or do I need to download the source and make 
changes?

Jim

Leif Mortenson wrote:
> Jim and all,
>    Ok.  This sounds like a good idea.  I took the opportunity to also 
> synchronize the
> unix and Windows command line syntaxes.  Their old formats are now 
> supported
> everywhere.
> 
>    Here is the new usage:
> -----
> C:\MyApp\bin>wrapper.exe
> Wrapper (Version 3.n.n) http://wrapper.tanukisoftware.org
> 
> Usage:
>  wrapper.exe <command> <configuration file> [configuration properties] 
> [...]
>  wrapper.exe <configuration file> [configuration properties] [...]
>     (<command> implicitly '-c')
>  wrapper.exe <command>
>     (<configuration file> implicitly 'wrapper.conf')
>  wrapper.exe
>     (<command> implicitly '-c' and <configuration file> 'wrapper.conf')
> 
> where <command> can be one of:
>  -c  --console run as a Console application
>  -t  --start   starT an NT service
>  -p  --stop    stoP a running NT service
>  -i  --install Install as an NT service
>  -r  --remove  Remove as an NT service
>  -q  --query   Query the current status of the service
>  -qs --querysilent Silently Query the current status of the service
>  -?  --help    print this help message
> 
> <configuration file> is the wrapper.conf to use.  Name must be absolute 
> or relative
>  to the location of wrapper.exe
> 
> [configuration properties] are configuration name-value pairs which 
> override values
>  in wrapper.conf.  For example:
>  wrapper.debug=true
> -----
> 
>    The Windows only commands are of course invalid on UNIX.
> 
>    This is all implemented and will be in the 3.2.1 release.   
> SourceForge's CVS is being
> stubborn at the moment though, so I'll have to commit it later.
> 
> Cheers,
> Leif
> 
> Jim Redman wrote:
>> Does anyone else have a use for the feature where the name of the 
>> config file maps to the name of the application?
>>
>> It allows two applications in the same directory without adding 
>> arguments to the application and so is much cleaner.  For example,
>>
>> MyApp.exe looks for MyApp.conf
>> AnotherApp.exe looks for AnotherApp.conf
>>
>> etc.  It then looks for wrapper.conf if the app-specific wrapper does 
>> not exist.
>>
>> We need to make this change to the lastest exe.  If it's of general 
>> interest, I'll try and do it cleanly and create a diff.  Otherwise 
>> I'll just hack it in there.
>>
>> Jim
>>
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live 
> webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

-- 
Jim Redman
(505) 662 5156 x85
http://www.ergotech.com