174 lines
7.3 KiB
TypeScript
Raw Normal View History

2025-02-25 20:40:47 +01:00
import type { Metadata } from "next"
2025-03-02 00:31:15 +01:00
import { Server } from "lucide-react"
2025-03-01 19:29:41 +01:00
import CopyableCode from "@/components/CopyableCode"
2025-02-25 20:40:47 +01:00
export const metadata: Metadata = {
title: "ProxMenux Post-Install: System Settings",
description:
"Detailed guide to the System Settings category in the ProxMenux post-install script for Proxmox VE optimization.",
2025-03-01 19:29:41 +01:00
openGraph: {
title: "ProxMenux Post-Install: System Settings",
description:
"Detailed guide to the System Settings category in the ProxMenux post-install script for Proxmox VE optimization.",
type: "article",
url: "https://macrimi.github.io/ProxMenux/docs/post-install/system",
images: [
{
url: "https://macrimi.github.io/ProxMenux/system-settings-image.png",
width: 1200,
height: 630,
alt: "ProxMenux Post-Install System Settings",
},
],
},
twitter: {
card: "summary_large_image",
title: "ProxMenux Post-Install: System Settings",
description:
"Detailed guide to the System Settings category in the ProxMenux post-install script for Proxmox VE optimization.",
images: ["https://macrimi.github.io/ProxMenux/system-settings-image.png"],
},
2025-02-25 20:40:47 +01:00
}
2025-03-02 00:31:15 +01:00
function StepNumber({ number }: { number: number }) {
return (
<div className="inline-flex items-center justify-center w-8 h-8 mr-3 text-white bg-blue-500 rounded-full">
<span className="text-sm font-bold">{number}</span>
</div>
)
}
2025-02-25 20:40:47 +01:00
export default function SystemSettingsPage() {
return (
<div className="container mx-auto px-4 py-8">
2025-02-25 20:55:48 +01:00
<div className="flex items-center mb-6">
<Server className="h-8 w-8 mr-2 text-blue-500" />
<h1 className="text-3xl font-bold">System Settings</h1>
</div>
2025-02-25 20:40:47 +01:00
<p className="mb-4">
2025-03-02 12:46:02 +01:00
The <strong>System Settings</strong> category includes core system configurations and optimizations for Proxmox VE,
focusing on performance, stability, and resource management.
2025-02-25 20:40:47 +01:00
</p>
2025-03-01 19:29:41 +01:00
<h2 className="text-2xl font-semibold mt-8 mb-4">Available Optimizations</h2>
2025-03-02 00:31:15 +01:00
<h3 className="text-xl font-semibold mt-16 mb-4 flex items-center">
<StepNumber number={1} />
Enable Fast Reboots
</h3>
<p className="mb-4">
2025-03-02 12:46:02 +01:00
This optimization enables <code>kexec</code>, allowing the system to boot directly into a new kernel
without going through the BIOS/firmware and bootloader.
2025-03-02 00:31:15 +01:00
</p>
<p className="mb-4">
2025-03-02 16:54:00 +01:00
<strong className="block">Why it's beneficial:</strong>
Fast reboots reduce system downtime during updates and maintenance.
2025-03-02 12:46:02 +01:00
This is particularly useful in virtualization environments where minimizing host downtime helps maintain service availability.
2025-03-02 00:31:15 +01:00
</p>
2025-03-02 01:14:53 +01:00
<p className="text-lg mb-2">This adjustment automates the following commands:</p>
2025-03-02 00:31:15 +01:00
<CopyableCode
code={`
sudo apt-get install -y kexec-tools
2025-03-01 19:55:22 +01:00
sudo systemctl enable kexec-pve.service
2025-03-02 00:31:15 +01:00
echo "alias reboot-quick='systemctl kexec'" >> ~/.bash_profile
`}
/>
2025-03-01 19:29:41 +01:00
2025-03-02 00:31:15 +01:00
<h3 className="text-xl font-semibold mt-16 mb-4 flex items-center">
<StepNumber number={2} />
Configure Kernel Panic Behavior
</h3>
<p className="mb-4">
2025-03-02 12:46:02 +01:00
This setting configures the system to automatically reboot after a <strong>kernel panic</strong> instead of remaining unresponsive.
2025-03-02 00:31:15 +01:00
</p>
<p className="mb-4">
2025-03-02 16:54:00 +01:00
<strong className="block">Why it's beneficial:</strong>
Automatic recovery reduces downtime and prevents the need for manual intervention,
2025-03-02 12:46:02 +01:00
which is critical in remote or unattended environments where physical access is limited.
2025-03-02 00:31:15 +01:00
</p>
2025-03-02 01:14:53 +01:00
<p className="text-lg mb-2">This adjustment automates the following commands:</p>
2025-03-02 00:31:15 +01:00
<CopyableCode
code={`
echo "kernel.panic = 10" | sudo tee /etc/sysctl.d/99-kernelpanic.conf
2025-03-01 19:55:22 +01:00
echo "kernel.panic_on_oops = 1" | sudo tee -a /etc/sysctl.d/99-kernelpanic.conf
2025-03-02 00:31:15 +01:00
sudo sysctl -p /etc/sysctl.d/99-kernelpanic.conf
`}
/>
<h3 className="text-xl font-semibold mt-16 mb-4 flex items-center">
<StepNumber number={3} />
Increase System Limits
</h3>
<p className="mb-4">
2025-03-02 12:46:02 +01:00
This optimization increases system resource limits, including the maximum number of <strong>file watches</strong> and <strong>open file descriptors.</strong>
2025-03-02 00:31:15 +01:00
</p>
<p className="mb-4">
2025-03-02 16:54:00 +01:00
<strong className="block">Why it's beneficial:</strong>
Higher limits enhance resource utilization, improving performance for applications
2025-03-02 12:46:02 +01:00
that monitor large numbers of files or handle high concurrent connections. This is essential
for servers running multiple VMs or containers.
2025-03-02 00:31:15 +01:00
</p>
2025-03-02 01:14:53 +01:00
<p className="text-lg mb-2">This adjustment automates the following commands:</p>
2025-03-02 00:31:15 +01:00
<CopyableCode
code={`
echo "fs.inotify.max_user_watches = 1048576" | sudo tee /etc/sysctl.d/99-maxwatches.conf
2025-03-01 19:55:22 +01:00
echo "* soft nofile 1048576" | sudo tee /etc/security/limits.d/99-limits.conf
2025-03-02 00:31:15 +01:00
sudo sysctl -p
`}
/>
<h3 className="text-xl font-semibold mt-16 mb-4 flex items-center">
<StepNumber number={4} />
Optimize Journald
</h3>
<p className="mb-4">
2025-03-02 12:46:02 +01:00
This setting configures <strong>systemd-journald</strong> to limit disk usage and optimize logging performance.
2025-03-02 00:31:15 +01:00
</p>
<p className="mb-4">
2025-03-02 16:54:00 +01:00
<strong className="block">Why it's beneficial:</strong>
Restricting log size prevents excessive disk consumption,
2025-03-02 12:46:02 +01:00
reducing the risk of system partitions filling up. Optimized logging also decreases I/O operations,
improving system performance, especially in disk-constrained environments.
2025-03-02 00:31:15 +01:00
</p>
2025-03-02 01:14:53 +01:00
<p className="text-lg mb-2">This adjustment automates the following commands:</p>
2025-03-02 00:31:15 +01:00
<CopyableCode
code={`
echo "SystemMaxUse=64M" | sudo tee -a /etc/systemd/journald.conf
sudo systemctl restart systemd-journald
`}
/>
<h3 className="text-xl font-semibold mt-16 mb-4 flex items-center">
<StepNumber number={5} />
Optimize Memory Management
</h3>
<p className="mb-4">
2025-03-02 12:46:02 +01:00
This optimization adjusts kernel parameters to improve <strong>memory allocation</strong> and <strong>system responsiveness.</strong>
2025-03-02 00:31:15 +01:00
</p>
<p className="mb-4">
2025-03-02 16:54:00 +01:00
<strong className="block">Why it's beneficial:</strong>
Efficient memory management prevents out-of-memory (OOM) conditions,
2025-03-02 12:46:02 +01:00
enhances stability, and optimizes resource allocation in virtualization environments.
This is particularly important for hosts running memory-intensive workloads or multiple VMs.
2025-03-02 00:31:15 +01:00
</p>
2025-03-02 01:14:53 +01:00
<p className="text-lg mb-2">This adjustment automates the following commands:</p>
2025-03-02 00:31:15 +01:00
<CopyableCode
code={`
echo "vm.swappiness = 10" | sudo tee /etc/sysctl.d/99-memory.conf
2025-03-01 19:55:22 +01:00
echo "vm.vfs_cache_pressure = 50" | sudo tee -a /etc/sysctl.d/99-memory.conf
2025-03-02 00:31:15 +01:00
sudo sysctl -p /etc/sysctl.d/99-memory.conf
`}
/>
2025-03-01 19:29:41 +01:00
<section className="mt-12 p-4 bg-blue-100 rounded-md">
<h2 className="text-xl font-semibold mb-2">Automatic Application</h2>
<p>
2025-03-02 00:31:15 +01:00
All of these optimizations are automatically applied when selected in the System section. This automation
ensures that these beneficial settings are applied consistently and correctly, saving time and reducing the
potential for human error during manual configuration.
2025-03-01 19:29:41 +01:00
</p>
</section>
2025-02-25 20:40:47 +01:00
</div>
2025-03-02 00:31:15 +01:00
)
}