Free Software -
Command line utilities
|
Written by Thomas
|
Thursday, 05 February 2009 17:22 |
Page 7 of 12
Each process task listed in ServiceProcesses in the [General] section requires its own process task section in the configuration file.
ApplicationName=<path string>
This is the full name and path of the application to run as a Windows service. If 'ApplicationName' contains relative path information the base folder is the folder in which ServiceExe.exe itself resides. The string <path string> supports embedded environment variables.
Examples:
ApplicationName=C:\Program files\MyApplication\MyApplication.exe ApplicationName=MyApplication.exe
By utilising the correct settings for 'ApplicationName' and 'CommandLine' it is also possible to install and run Windows command line scripts as Windows services.
CommandLine=<parameter string>
The command line parameters for the application specified with 'ApplicationName'. The default is an empty string, i.e. no parameters are passed to the application.
By utilising the correct settings for 'ApplicationName' and 'CommandLine' it is also possible to install and run Windows command line scripts as Windows services.
The following example installs and runs the command line interpreter CMD.EXE as a Windows service. When the service is started, the command line script MyBatchFile.cmd is executed. When MyBatchFile.cmd terminates the entrie service stops.
ApplicationName=%ComSpec% CommandLine=/C MyBatchFile.cmd
CurrentDirectory=<string>
ServiceExe sets the current working directory for the application supposed to run as a service to the string provided with 'CurrentDirectory'. This setting supports embedded environment variables. The default is the folder/directory in which ServiceExe.exe itself resides.
Examples:
CurrentDirectory=C:\Program files\MyApplication CurrentDirectory=%windir% CurrentDirectory=%TEMP%
Download ServiceExe.zip (0.11 MiB = 108.4 KiB = 111,041 bytes)
|
Last Updated on Thursday, 05 July 2012 13:25 |
to post comments.