Tree: ff89edf127

cpu

cryptopp

debian

gha

i2pcontrol

master

moduled

openssl

socks5

static-build

webconsole-inja

0.1.0

0.10.0

0.2.0

0.3.0-homebrew

0.4.0

0.5.0

0.6.0

0.7.0

0.8.0

0.9.0

2.1.0

2.10.0

2.10.1

2.10.2

2.11.0

2.12.0

2.13.0

2.14.0

2.15.0

2.16.0

2.17.0

2.18.0

2.19.0

2.2.0

2.20.0

2.21.0

2.21.1

2.22.0

2.23.0

2.24.0

2.25.0

2.26.0

2.27.0

2.28.0

2.29.0

2.3.0

2.30.0

2.31.0

2.32.0

2.32.1

2.33.0

2.34.0

2.35.0

2.36.0

2.37.0

2.38.0

2.39.0

2.4.0

2.40.0

2.41.0

2.42.0

2.42.1

2.43.0

2.44.0

2.45.0

2.45.1

2.46.0

2.46.1

2.47.0

2.48.0

2.49.0

2.5.0

2.5.1

2.50.0

2.50.1

2.50.2

2.51.0

2.52.0

2.53.0

2.53.1

2.54.0

2.6.0

2.7.0

2.8.0

2.9.0

v0.3.0-1stbinrelease

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'ff89edf127'

${ noResults }

Commit Graph

8 Commits (ff89edf1272c0146e05f4381193ab53ecad7b75e)

Author	SHA1	Message	Date
R4SAS	3d7e93a688	systemd: use SIGTERM instead SIGQUIT, indent UPNP code, make client target ... Signed-off-by: R4SAS <r4sas@i2pmail.org>	4 years ago
Zetok Zalbavar	2c9fa2f738	Fix and update i2pd.service ... - /var/run on distros with systemd is a symlink to /run , hence the path changes. - Remove unnecessary runtime dependency on `/bin/kill` which is provided by `procps` and might not be available on minimal installs (e.g. containers). Instead use `/bin/sh` which has a built-in `kill`. - `PrivateDevices=yes` causes i2pd to fail to start on latest Debian unstable. Service exits with the following: ``` i2pd.service: Failed to execute command: Operation not permitted i2pd.service: Failed at step EXEC spawning /usr/sbin/i2pd: Operation not permitted i2pd.service: Control process exited, code=exited, status=203/EXEC i2pd.service: Failed with result 'exit-code'. Failed to start I2P Router written in C++. ``` According to `man systemd.exec` exit code 203 corresponds to the `execve(2)` system call failing. So it looks like i2pd tries to do something it shouldn't be doing. The proper fix would be in i2pd, but who knows how long that would actually take, so to allow people to actually launch i2pd in meanwhile the line has been removed from the service file. Also, surprisingly, right after installing i2pd it started without any problems, and only after restarting the box i2pd started to fail for no apparent reason.	5 years ago
R4SAS	b7940e0002	add tunnels.d to packages	6 years ago
R4SAS	a188de2e5c	increase limits by default, fix symbolic links, change rules	6 years ago
yangfl	c0436297c2	fix typo in systemd service type	7 years ago
yangfl	f06c8710be	fix systemd service type	7 years ago
Fabrice Fontaine	b0781668e2	Create LogsDirectory in i2pd.service ... Create /var/log/i2pd through LogsDirectory parameter of systemd and set its permission to 0700 through LogsDirectoryMode. Indeed, this directory must be created with the correct permission as it is used in ExecStart command Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>	7 years ago
yangfl	319d748639	i2pd.service: do not block system shutdown for 10 min	7 years ago
R4SAS	13d174c09c	add tunconf in systemctl service file	7 years ago
yangfl	18b6353803	fix typo	7 years ago
kayrus	4267063dba	Create run dir for i2pd process in systemd unit file	7 years ago
atnaguzin	8b0ce30dfc	systemd unit, debian patch fix, makefile last-dist added, package log&pid folder edited	8 years ago