1.2 KiB
1.2 KiB
title | date | url | layout | category | image | description |
---|---|---|---|---|---|---|
Proxmox 5 standalone instance optimizations | 2019-01-11 | proxmox-5-standalone-instance-optimizations | post | Hacking | /img/blog/proxmox-5-standalone-instance-optimizations.png | A (potentially wrong) write-up about Proxmox standalone instance optimizations |
Introduction
This is (already) the third blog post about Proxmox, and it's what about you could do on standalone Proxmox instances.
When you don't use Proxmox clustering features, you may want to stop some running services, polluting your system logs.
⚠️ This has to be considered very experimental and don't expect replication nor high-availability functionalities to work once you have disabled these services. ⚠️
The procedure
{% highlight bash %} systemctl disable --now pve-ha-crm.service systemctl disable --now pve-ha-lrm.service systemctl disable --now pvesr.timer systemctl disable --now corosync.service {% endhighlight %}
Conclusion
Comments and feedbacks are very welcome.