https://sourceforge.net/p/wrapper/feature-requests/128/Recent changes to 128: windows: add remote access to commandline interfaceenWed, 09 Feb 2011 07:47:58 -0000https://sourceforge.net/p/wrapper/feature-requests/128/he wrapper commands relating to the windows service \(http://wrapper.tanukisoftware.com/doc/german/launch-win.html\#exe\) are of restricted use because the service is usually at a \(remote\) server and to issue service related commands you have to login at the remote server or use other tools. I would like that the wrapper is able to connect to a remote service manager to issue service related commands all commands use the parameters found in the wrapper.conf. To access a remote service its not really required to enhance this logic. e.g. wrapper -p N:\path\wrapper.conf if wrapper.exe detects that the effective path to wrapper.conf is at a network drive \(i.e. detects that N is a network drive\) then the remote servername could be determined using the properties of the network drive and the command could be issued remote. This could be used for following commands: -t --start starT an NT service -a --pause pAuse a started NT service -e --resume rEsume a paused NT service -p --stop stoP a running NT service -r --remove Uninstall/Remove as an NT service -l=<code> --controlcode=<code> send a user controL Code to a running NT service -q --query Query the current status of the service -qs --querysilent Silently Query the current status of the service \(is this a service related command??\) -d --dump request a thread Dump under additional conditions even -install commands could be done remote if there are concerns about security and/or backwards compatibility this feature could be only enabled if a additional environment property is set: e.g.: wrapper.ntservice.enable\_remote\_access thinkable values could be 0 do not enable remote operate as before 1 enable, if remote access is detected: allow detection of server name and access remote 2:<server name> do not detect server name, access <server name> always if remote \( this if detection of the server name maybe error prone\) with the above semantics the command line interface does not need to be enhanced \(exception maybe -install of remote service\) and operates remote in the same manner as locally. Even the existing scripts may be used remote without modification What do you think about it? CharlycharlyWed, 09 Feb 2011 07:47:58 -0000https://sourceforge.neta72d5444443399ed8acb8775d69c1258db7192bf