From bb86769ac0a7600a83db589cf56c2df1d490b497 Mon Sep 17 00:00:00 2001 From: R4SAS Date: Mon, 6 Jun 2022 18:28:42 +0300 Subject: [PATCH] Add '--service' option for usage of ProgramData directory (since 2.43.0!) --- Setting-up-i2pd-as-Windows-Service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Setting-up-i2pd-as-Windows-Service.md b/Setting-up-i2pd-as-Windows-Service.md index 2acc82e..f47bb63 100644 --- a/Setting-up-i2pd-as-Windows-Service.md +++ b/Setting-up-i2pd-as-Windows-Service.md @@ -9,7 +9,7 @@ Fire up elevated Command Prompt (Win+X, A since Windows 8) _Note: Mind spaces after `=`!_ ``` -sc create i2pdService binPath= "C:\soft\i2pd\i2pd.exe --daemon" DisplayName= "i2pd router service" obj= "NT AUTHORITY\LocalService" start= "auto" +sc create i2pdService binPath= "C:\Program Files\i2pd\i2pd.exe --daemon --service" 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`. 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.