3 ms·
It writes too many logs. It's always log writes, except when it's the DNS.
by ggm 2y ago
It writes too many logs. It's always log writes, except when it's the DNS.
- LinuxBender 2y agoI've not yet tried out Proxmox. Can you define where the Proxmox logs go? If so one could mount tmpfs ramdisks at startup and point the logs there with an aggressive log rotation cron to keep the usage low. If this is just syslog one could mount /var/log as tmpfs accepting that logs go away if one reboots or send syslog elsewhere over the network to cheap storage. # grep "/var/log" /etc/fstab tmpfs /var/log tmpfs defaults,nosuid,nodev,noatime,size=1g 0 0
- ggm 2y agoNot a proxmox user but that's certainly where I'd go, if I was: write to memory via an fs abstraction, get data off into another place via network if you need it. There's also the noatime flag, for unavoidable writes to local disk: avoid the update to dir stat() state if you can.