e1lama/i2pd
1
0
Fork 0
mirror of https://github.com/PurpleI2P/i2pd.git synced 2025-03-07 06:09:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Setting up i2pd as Windows Service (markdown)

R4SAS
2022-02-28 22:53:15 +03:00
parent 7827cdcf4e
commit 805647a2cc
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
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 (<kbd>Win+X</kbd>, <kbd>A</kbd> 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)