Re: [Wrapper-user] Configuration Properties

[Leif M. <le...@ta...>]

Barry,
    The Wrapper does not have a command on UNIX version to stop
another process.   The shell script will accept a stop command that
will do this however.   The script is considered part of the "wrapper"
solution.

    There are a number of ways to stop a wrapper process.   By
default you can send it a TERM signal.  The wrapper can be
configured to ignore these signals however.

    Another method is to specify an anchor file using the
wrapper.anchorfile=./wrapper.anchor property.  The wrapper will
create the anchor file on startup.  If you delete it, the wrapper will
shutdown cleanly.

    Hope that helps.

Cheers,
Leif

Barry Molof wrote:
> Ok, I see how to start a unix daemon using wrapper directly with 
> wrapper.daemonize=TRUE.  However, once it is started, can I use the 
> wrapper directly to stop the daemon?
>  
> Barry
>
>  
> On 6/7/07, *Leif Mortenson* <le...@ta... 
> <mailto:le...@ta...>> wrote:
>
>     Barry,
>     Yes, it works the same on all platforms.  %VAR% syntax is used rather
>     than the standard UNIX $VAR format so the wrapper.conf file will work
>     on all platforms without modification.
>
>     Take a look at this page for more details:
>     http://wrapper.tanukisoftware.org/doc/english/props-envvars.html
>     <http://wrapper.tanukisoftware.org/doc/english/props-envvars.html>
>
>     Cheers,
>     Leif
>
>     Barry Molof wrote:
>     > Hello Leif,
>     >
>     > Could I get the same functionality in Linux\Solaris?  Have a common
>     > wrapper.conf file that includes another app specific conf file
>     based
>     > on an environment variable.
>     >
>     > Thanks,
>     > Barry
>     >
>     > On 6/4/07, *Barry Molof* <bm...@gm...
>     <mailto:bm...@gm...> <mailto:bm...@gm...
>     <mailto:bm...@gm...>>>
>     > wrote:
>     >
>     >     I got it working.  The bat file to install the service that
>     comes
>     >     with the distribution does not allow you to add extra
>     parameters.
>     >     If I do as you say and run the wrapper.exe directly to
>     install it
>     >     then everything works great.
>     >
>     >     Thank you for your help.
>     >
>     >
>     >     On 6/4/07, *Barry Molof* <bm...@gm...
>     <mailto:bm...@gm...>
>     >     <mailto:bm...@gm... <mailto:bm...@gm...>>> wrote:
>     >
>     >         This didn't seem to work.  I have a wrapper.conf with only
>     >         #include %WRAPPER_CONF_INCLUDE% and I run the NT Service
>     >         install bat file as:
>     >
>     >         InstallService.bat .\wrapper.conf
>     >         set.WRAPPER_CONF_INCLUDE=..\agent\conf\wrapper.conf
>     >
>     >         When I do this, it looks like it is never reading the
>     >         agent\conf\wrapper.conf file at all since a service called
>     >         wrapper is installed instead of the name I am giving it
>     in the
>     >         application conf file.
>     >
>     >         On 6/4/07, *Leif Mortenson* < le...@ta...
>     <mailto:le...@ta...>
>     >         <mailto:le...@ta...
>     <mailto:le...@ta...>>> wrote:
>     >
>     >             Barry,
>     >             > When running wrapper.exe directly you have the
>     choice to
>     >             specify
>     >             > configuration properties on the command line. Is it
>     >             possible to
>     >             > install a windows service using the Install bat
>     file and
>     >             to specify
>     >             > configuration properties to set when it starts?
>     >             Anything placed on the command line when the service in
>     >             installed
>     >             will be placed into the registry and used again when
>     the
>     >             service is
>     >             started.
>     >             >
>     >             > What I would like to do is have a common conf file
>     that
>     >             is called
>     >             > first which would then include another application
>     >             specific conf file
>     >             > that is pointed to by a configuration property
>     specified
>     >             when the
>     >             > wrapper.exe service is called. Is this possible?
>     >             Try this.
>     >             Start by specifying the following to include your config
>     >             file from the
>     >             primary wrapper.conf:
>     >             ---
>     >             #include %WRAPPER_CONF_INCLUDE%
>     >             ---
>     >
>     >             Then put the following on the command line when
>     installing
>     >             the service:
>     >             wrapper.exe -i ..\conf\wrapper.conf
>     >             set.WRAPPER_CONF_INCLUDE=../myapp.conf
>     >
>     >             Cheers,
>     >             Leif
>