Having a cache_dir at all is non-default. Squid-3 default is to run with a memory-only cache. The /var/spool/squid path is used as default run- time working directory.
Which reminds me the proxies low-privilege user account is tied via home directory to the location the original machine install was done with. That probably has not been updated since before Trusty. Symlinks and mount points, either on the cache_dir directory, or below it need to be accounted for. As do SELinux policies, AppArmour policies - both the system ones and custom changes which do not show up in the squid.conf paths. Then there is the issue of other custom tools interacting with the cache_dir data. Not common but when it does happen it's usually custom software outside the package tracking system, which we dont have a clue about whether it can cope with the move. IMHO just leave it, the gain is cosmetic at best and surprisingly hard to do correctly without local knowledge only the admin has. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613914 Title: squid upgrade fails when user has custom cache_dir To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1613914/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
