From 805647a2cc8b04bc674d6c42df6d2be2ec1554b9 Mon Sep 17 00:00:00 2001 From: R4SAS Date: Mon, 28 Feb 2022 22:53:15 +0300 Subject: [PATCH] Updated Setting up i2pd as Windows Service (markdown) --- Setting-up-i2pd-as-Windows-Service.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Setting-up-i2pd-as-Windows-Service.md b/Setting-up-i2pd-as-Windows-Service.md index 0cd5b88..2acc82e 100644 --- a/Setting-up-i2pd-as-Windows-Service.md +++ b/Setting-up-i2pd-as-Windows-Service.md @@ -2,19 +2,19 @@ One can set up i2pd as a Windows Service. This way it will run in the background without any annoying windows or tray icons. It can be controlled with a standard [*Services*](https://technet.microsoft.com/en-us/library/cc772408.aspx) snap-in of *Microsoft Management Console (MMC)*. -While it is possible to install service using corresponding [command line option](https://github.com/PurpleI2P/i2pd/blob/openssl/docs/configuration.md), standard tools like [sc](https://technet.microsoft.com/en-us/library/cc990289.aspx) can be used as well. Currently, this gives some flexibility as there in no need to add `daemon = yes` in config, but `--daemon` can be supplied as an argument. +For registering i2pd as Windows Service, you can use standard tool [sc](https://technet.microsoft.com/en-us/library/cc990289.aspx). ### Service installation Fire up elevated Command Prompt (Win+X, A since Windows 8) and type in the following making sure you use the correct path where you have `i2pd.exe`. _Note: Mind spaces after `=`!_ ``` -sc create i2pdService binPath= "C:\dev\i2p\appveyor\i2pd.exe --daemon" DisplayName= "i2pd router service" obj= "NT AUTHORITY\LocalService" +sc create i2pdService binPath= "C:\soft\i2pd\i2pd.exe --daemon" DisplayName= "i2pd router service" obj= "NT AUTHORITY\LocalService" start= "auto" ``` -The service will run under special *LocalService* user account. Its configuration folder is likely `C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\i2pd`, but if you place `i2pd.conf` into binary directory, it would start work in same directory where `i2pd.exe` is placed. +The service will run under special *LocalService* user account. Its configuration folder is likely `C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\i2pd`. You will need elevated privileges to access LocalService AppData location. You may find it handy to use [Far File Manager](http://www.farmanager.com) or alike for such manipulations. -You will need elevated privileges to access LocalService AppData location. You may find it handy to use [Far File Manager](http://www.farmanager.com) or alike for such manipulations. +But if you place `i2pd.conf` into binary directory, it would start work in same directory where `i2pd.exe` is placed. ![screenshot](Setting-up-i2pd-as-Windows-Service.png)