On 29 Dec 15:15, Chris G wrote:
On Sat, Dec 29, 2007 at 11:58:54AM +0000, Paul wrote:
On Saturday 29 December 2007 10:39, Chris G wrote:
That won't matter as you are already backing /var up aren't you?
Yes, but that *shouldn't* be necessary. The whole point of /var according to the standards is that there is *nothing* there that needs backing up
Disagree - /var/mail, /var/lib, and possibly /var/cache should be backed up as much of the meta data related to installed packages reside there. Backing up /var/log is advisable should you ever need to do any forensics after a system has been hacked.
No no no... backing up /var/log is less important if you have syslog configured to also log to a remote syslog daemon on a different machine. That way you should have logs right to the point that it was broken.
Ah but /var/mail in particular is suggested may be a link to somewhere in the /home hierarchy isn't it?
I've never seen a system configured that way. That way madness lies. /var/spool/mail is a symlink to /var/mail on a lot of the systems I use.
Most people wanting to move mail over to home deliver to a maildir these days, ~/Maildir/ being the usual place, and certainly how I configure new machines these days.
[current spec can be found at http://www.pathname.com/fhs/pub/fhs-2.3.html ]
As for web files (html, tarballs, general "stuff"), much of it goes in /var/www, some in /home/<usr>/stuff, and a great gob of files in /debian - Anything outside of /var/www gets symlinks.. Bottom line, your system, your choice ;-)
Exactly, but I'm trying to come up with a strategy that isn't just a confused mess.
So, use: /srv/websites/tld/domain/subdomain eg: /srv/websites/uk/co/sommitrealweird/www or: /srv/websites/uk/co/www.sommitrealweird.co.uk
Just decide on a layout and have done with it. (Personally, I have lots of sites all over the place, on this particular box I have a django server that is fronted by apache's mod_proxy, but the django instance is running using fastcgi fronted by lighttpd, the data is in /home/brettp/django/alug, which then has code in the alug subdirectory, images/other media in alug-media and templates for use in the code in alug-templates. My main website is hosted on another box, where it is sitting in my home directory as a directory called srw_html, I have symlinked public_html to that as I class it as the main site and where I'm most likely to want to put things on that box).
Ho hum,