Helmut Grohne <hel...@subdivi.de> writes: > So you already pointed out that we are talking about a cache, but > still use /var/lib. Why? I suggested /var/cache/munin/graph and still > think that it is a better place, because your backup solution does not > need to back up those graphs.
The different locations are rather well documented in the FHS, so we'll just take a look at the description, demands and limitations of each, and figure out which suits munin best. http://www.pathname.com/fhs/pub/fhs-2.3.html ,---- | /var/cache : Application cache data | | Purpose | | /var/cache is intended for cached data from applications. Such data is | locally generated as a result of time-consuming I/O or calculation. | The application must be able to regenerate or restore the data. Unlike | /var/spool, the cached files can be deleted without data loss. The | data must remain valid between invocations of the application and | rebooting the system. | | Files located under /var/cache may be expired in an application | specific manner, by the system administrator, or both. The application | must always be able to recover from manual deletion of these files | (generally because of a disk space shortage). No other requirements | are made on the data format of the cache directories. | | Rationale | | The existence of a separate directory for cached data allows system | administrators to set different disk and backup policies from other | directories in /var. | `---- ,---- | /var/lib : Variable state information | | Purpose | | This hierarchy holds state information pertaining to an application or | the system. State information is data that programs modify while they | run, and that pertains to one specific host. Users must never need to | modify files in /var/lib to configure a package's operation. | | State information is generally used to preserve the condition of an | application (or a group of inter-related applications) between | invocations and between different instances of the same application. | State information should generally remain valid after a reboot, should | not be logging output, and should not be spooled data. | | An application (or a group of inter-related applications) must use a | subdirectory of /var/lib for its data. There is one required | subdirectory, /var/lib/misc, which is intended for state files that | don't need a subdirectory; the other subdirectories should only be | present if the application in question is included in the | distribution. [38] | | /var/lib/<name> is the location that must be used for all distribution | packaging support. Different distributions may use different names, of | course. | `---- -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
