Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upHow do I turn permanently turn off a service in an AppVM #1000
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
This type of questions should be sent to qubes-users mailing list. |
marmarek
closed this
May 20, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
cfcs commentedMay 20, 2015
I couldn't find any information on this, perhaps I searched for the wrong things, but I'd like to turn off some services to preserve memory and CPU usage in my AppVMs.
Example: My NetVM listens on these ports - I would prefer it not listening to anything. And yes, I could firewall that off, but maintaining a reliable firewall setup in Qubes is a challenge I've given up on:
Other examples of
systemctlservices / targets I don't see a reason to run in each and every AppVM:I can think of two hacks to do this:
I actually think the problem of /etc being read-only is relevant to a lot of other use cases. For example, if I want a MySQL/RabbitMQ/Redis/PostgreSQL/whatever install in a development VM, I have to manually add symlinks to /rw in the template for each of them, for any configuration files they may or may not already have created. Any users or temporary mounts and so on also have to either be created on boot through /rw/rc.config or be a permanent part of every AppVM using the same template.
I realize that making it writable also comes with its share of problems since that prevents templates updates from adding new things. Could some kind of permanent "union" of the template copy-on-write directory be conceived?
It's entirely possible that I'm missing something -- what do other people do?