also sprach Stefan Fritsch <sf@sfritsch.de> [2016-11-13 11:34 +0100]:
> Do you have mod_cache_disk enabled? If not then htcacheclean being started
> would be a bug in apache2's upgrade logic.
I do have the module enabled, of course.
> > By the filesystem hierarchy standard, nothing in /var/cache must
> > be taken for granted. This means that the tool either needs to
> > fail gracefully, or create the missing directory/file.
>
> It's not clear what the best behavior is, here. The dir needs to
> be configured in apache's config, too, and the dir missing could
> point to a mis-configuration. In that case, aborting with an error
> is very useful.
The directory is configured by default if I enable the module.
However, it is not created.
I think the best way to solve this would be to warn & fail if the
configured directory does not exist UNLESS it is the default
/var/cache/apache2/mod_cache_disk, in which case I think the apache2
startup process should create the directory, so that it works out of
the box even with /var/cache on tmpfs.
--
.''`. martin f. krafft <madduck@d.o> @martinkrafft
: :' : proud Debian developer
`. `'` http://people.debian.org/~madduck
`- Debian - when you have better things to do than fixing systems
$complex->{'data'}[$structures][$in_perl] = @{$can{'be'}->[$painful]};
Attachment:
digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)