Add pfSense NVMe cache overlay documentation #45 - #46
Conversation
Sorry, something went wrong.
Add instructions for using nullfs with Squid on pfSense. Squid different cache location and management.
This update provides a detailed description of using a nullfs overlay for Squid cache relocation on pfSense systems, including a script for automation and notes on limitations regarding cache clearing.
Document Squid cache relocation using nullfs
This document provides a comprehensive guide on configuring Squid for multi-worker operation on pfSense, detailing both recommended and advanced methods for disk caching.
Updated section headers and improved clarity of instructions regarding the cron file and testing.
|
I closed #45 and this has all the updated items |
Sorry, something went wrong.
Thank you. I updated this PR title/description (that should become the future official commit message when this PR is merged) accordingly. Please adjust further as needed. |
Sorry, something went wrong.
|
|
||
| ## Option 2 (Advanced): Per-Worker Disk Cache Using Macros | ||
|
|
||
| ### ⚠️ Advanced / Experimental |
There was a problem hiding this comment.
Conditional per-worker cache_dir directives are not supported by the Squid Project. The exact effects of using such directives depend on Squid version. They may include stale cache entries and crashes. Squid does not refuse to start with such configurations (for now), but YMMV.
It would be nice if this example warned readers that they are looking at a dangerous and unsupported hack (rather than some new/experimental feature that should already work OK in many cases and will get better with time).
Sorry, something went wrong.
This document provides a script for creating a filesystem overlay using nullfs to mount an alternate NVMe-backed directory as the Squid cache location on pfSense systems. It includes usage instructions and a cron job setup.