From 7827cdcf4e43802113e861c1dea314633065a56d Mon Sep 17 00:00:00 2001 From: R4SAS Date: Wed, 23 Feb 2022 23:18:14 +0300 Subject: [PATCH] Updated Setting up i2pd as Windows Service (markdown) --- Setting-up-i2pd-as-Windows-Service.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Setting-up-i2pd-as-Windows-Service.md b/Setting-up-i2pd-as-Windows-Service.md index 97a0cce..0cd5b88 100644 --- a/Setting-up-i2pd-as-Windows-Service.md +++ b/Setting-up-i2pd-as-Windows-Service.md @@ -13,6 +13,7 @@ sc create i2pdService binPath= "C:\dev\i2p\appveyor\i2pd.exe --daemon" DisplayNa ``` 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)