1
21.1 Legacy Series / Re: Limit size for '/var RAM disk' option
« on: July 02, 2021, 04:11:45 am »
Understandably the primary concern of imposing limits on a tmpfs-backed `/var` is running out of disk space when performing updates. Looking at my system, it appears though the directories `pkg` uses are already symlinked to non-tmpfs locations. Specifically cache (PKG_CACHEDIR)
and database (PKG_DBDIR)
Are all aspects of OPNsense updates performed via `pkg`? If so updates via `pkg` should be unaffected by running out of space on tmpfs-backed `/var`. (Then running out of space on the primary disk is the concern, and you've got a whole bag of other problems.) If there's some other update mechanism employed, could the relevant cache/database locations be changed to somewhere on the primary disk?
Code: [Select]
root@OPNsense:~ # ls -l /var/cache/pkg
lrwxr-xr-x 1 root wheel 19 Jun 30 23:55 /var/cache/pkg -> /root/var/cache/pkg
and database (PKG_DBDIR)
Code: [Select]
root@OPNsense:~ # ls -l /var/db/pkg
lrwxr-xr-x 1 root wheel 16 Jun 30 23:55 /var/db/pkg -> /root/var/db/pkg
Are all aspects of OPNsense updates performed via `pkg`? If so updates via `pkg` should be unaffected by running out of space on tmpfs-backed `/var`. (Then running out of space on the primary disk is the concern, and you've got a whole bag of other problems.) If there's some other update mechanism employed, could the relevant cache/database locations be changed to somewhere on the primary disk?