32 lines
1.2 KiB
Markdown
32 lines
1.2 KiB
Markdown
---
|
|
title: "Proxmox 5 standalone instance optimizations"
|
|
date: 2019-01-11
|
|
url: proxmox-5-standalone-instance-optimizations
|
|
layout: post
|
|
category: Hacking
|
|
image: /img/blog/proxmox-5-standalone-instance-optimizations.png
|
|
description: "A (potentially wrong) write-up about Proxmox standalone instance optimizations"
|
|
---
|
|
|
|
[](/img/blog/proxmox-5-standalone-instance-optimizations.png)
|
|
|
|
### 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.
|
|
|
|
:warning: **This has to be considered very experimental and don't expect replication nor high-availability functionalities to work once you have disabled these services.** :warning:
|
|
|
|
### 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.
|