mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-12-30 09:46:28 -05:00
2d158b8ab2
It's wasn't perfectly clear that the 30_qubes.conf file should be created in the targeted VM, not in dom0
835 B
835 B
layout | title | permalink | redirect_from | |||
---|---|---|---|---|---|---|
doc | Qubes Service | /doc/qubes-service/ |
|
Usage documentation is on qvm-service manual page. There are also described predefined services.
Under the hood enabled service in VM is signaled by file in /var/run/qubes-service. This can be used to implement almost enable/disable per-VM switch controlled by dom0. Adding support for systemd services is pretty simple:
In the VM, create /etc/systemd/system/<service name>.service.d/30_qubes.conf
file
containing (you may need to create a directory for this file first):
[Unit]
ConditionPathExists=/var/run/qubes-service/<service name>
This will cause service to be started only when you enable it with qvm-service for this VM.