Qubes/core-agent-linux
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
e660c4a05f
core-agent-linux/vm-systemd/qubes-updates-proxy.service

15 lines
426 B
SYSTEMD
Raw Normal View History

Rename qubes-yum-proxy service to qubes-updates-proxy It is no longer Fedora-only proxy, so rename to not confuse the user. Also documentation refer to it as "updates proxy" for a long time.
2014-09-27 00:11:10 +02:00
[Unit]
Description=Qubes updates proxy (tinyproxy)
ConditionPathExists=|/var/run/qubes-service/qubes-updates-proxy
network: use own iptables service instead of repurposing existing one There were multiple problems with reusing existing one: - need to sync with upstream changes (configuration path etc) - conflicts resolution on updates - lack of iptables --wait, which causes firewall fail to load sometimes QubesOS/qubes-issues#1067
2015-08-04 17:15:01 +02:00
After=qubes-iptables.service
Rename qubes-yum-proxy service to qubes-updates-proxy It is no longer Fedora-only proxy, so rename to not confuse the user. Also documentation refer to it as "updates proxy" for a long time.
2014-09-27 00:11:10 +02:00
[Service]
ExecStartPre=/usr/lib/qubes/iptables-updates-proxy start
Use exec to ease systemd handling the tinyproxy process From Marek's comments
2019-04-17 11:37:03 +02:00
ExecStart=/usr/lib/qubes/tinyproxy-wrapper -d -c /etc/tinyproxy/tinyproxy-updates.conf
Rename qubes-yum-proxy service to qubes-updates-proxy It is no longer Fedora-only proxy, so rename to not confuse the user. Also documentation refer to it as "updates proxy" for a long time.
2014-09-27 00:11:10 +02:00
ExecStopPost=/usr/lib/qubes/iptables-updates-proxy stop
Restart=on-failure
RestartSec=5s
[Install]
WantedBy=multi-user.target
Reference in New Issue Copy Permalink