From d971b4960674896c9bfd76fd8559d2e591d78144 Mon Sep 17 00:00:00 2001 From: R4SAS Date: Wed, 23 Feb 2022 23:17:41 +0300 Subject: [PATCH] Updated Setting up i2pd as Windows Service (markdown) --- Setting-up-i2pd-as-Windows-Service.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Setting-up-i2pd-as-Windows-Service.md b/Setting-up-i2pd-as-Windows-Service.md index bcb0d6d..97a0cce 100644 --- a/Setting-up-i2pd-as-Windows-Service.md +++ b/Setting-up-i2pd-as-Windows-Service.md @@ -12,8 +12,8 @@ _Note: Mind spaces after `=`!_ sc create i2pdService binPath= "C:\dev\i2p\appveyor\i2pd.exe --daemon" DisplayName= "i2pd router service" obj= "NT AUTHORITY\LocalService" ``` -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 this location. You may find it handy to use [Far File Manager](http://www.farmanager.com) or alike for such manipulations. +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. +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. ![screenshot](Setting-up-i2pd-as-Windows-Service.png)