Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#58845 - [sshuttle] Systemd service file is broken
Attached to Project:
Community Packages
Opened by desbma (desbma) - Saturday, 02 June 2018, 21:25 GMT
Last edited by Felix Yan (felixonmars) - Sunday, 03 June 2018, 15:41 GMT
Opened by desbma (desbma) - Saturday, 02 June 2018, 21:25 GMT
Last edited by Felix Yan (felixonmars) - Sunday, 03 June 2018, 15:41 GMT
|
DetailsThe systemd service file for this package was recently changed to use 'Type=notify" as recommended by the sshuttle authors (see https://bugs.archlinux.org/task/56086).
However, the service file also needs the line `NotifyAccess=all`, otherwise Systemd will not receive the "ready" notification from shuttle, and will kill the process after a time out. See https://github.com/sshuttle/sshuttle/issues/238 for more info, and the fix. This is not an upstream bug, because the Systemd service file is a downstream addition (although mentioned in the sshuttle docs). Also, please add the 'After=network.target' dependency, as recommended in the sshuttle docs, and as asked in the previous Arch issue. Thanks |
This task depends upon
Closed by Felix Yan (felixonmars)
Sunday, 03 June 2018, 15:41 GMT
Reason for closing: Fixed
Additional comments about closing: 0.78.4-3
Sunday, 03 June 2018, 15:41 GMT
Reason for closing: Fixed
Additional comments about closing: 0.78.4-3