Is there any config for ensuring Super Cache files could be served/retained (and perhaps a file system
touch called on the file when this event is triggered, so the CACHE file 'appears' to be newer than it is):
`<!-- Page not cached by WP Super Cache. No closing HTML tag. Check your theme. -->'
We had a problem where portions of our theme (the header & footer, which don't change often) was being generated by code mounted on a failing hardware device. However the volume WordPress was installed in was working fine. The blogs were effectively down, but if WordPress could've continued to serve from /wp-content/cache/supercache, the sites would've appeared to be online. Unfortunately, the blogs were serving the failed, incomplete version of HTML, instead of the cached files.
The site(s) would've appeared to be online if WP Super Cache continued to serve the old, cached versions of the files, but it wouldn't.
Would 'Lockdown' have effectively done what I'm asking?
Of course, admins tend to want to be notified if this sort of thing is happening, so it'd be nice to have some sort of alert (in WP-Admin or via email) when this is triggered automatically.
Please let me know if this makes sense.