[RFC] /var versus /srv

Alexander Boström abo at kth.se
Fri Sep 28 07:40:00 UTC 2007

fre 2007-09-28 klockan 03:07 -0400 skrev Casey Dahlin:

> There's been enough reasons in this thread, just a matter of aggregating 
> them a bit. Immediately to mind are the divergent backup considerations.
> >       * List of directories in /var that are "wrong".
> >   
> /var/www, /var/ftp, /var/lib/mysql right off the top of my head. There's 
> probably more. Let's keep going


> One (rather extreme) way to look at it is that /var contains information 
> that should be stored in RAM except for 2 considerations: 1) it is too 
> large, 2) its relevance may extend beyond the life of the process or 
> across reboots. /var is a place for the application to write down what 
> it is actively in the process of doing or where it left off when it last 
> terminated. (This is how it SHOULD be IMHO. For now we should try not to 
> break FHS beyond what we're doing now).

Well, this seems to be spot on the current usage of /var/lib/mysql and
also with the FHS's definition of /var/lib (*), so I don't really see
why you think /var/lib/mysql is wrong. If you want to move /var/www to
say /var/lib/www then that seems more in line with your idea of /var,



More information about the fedora-devel-list mailing list