You are not logged in.
I'm running a server which provides data files, primarily via samba and apache, for the entire office. I've put the data files in various places on previous machines, but I'm trying to figure out where they really belong.
Everybody writes files to the server, and everybody needs to be able to access those files. I thought to put them in /home, but since they really don't belong to any particular user, is that where they should go? I thought under /srv, but more reading makes me think that is inappropriate too. Perhaps they belong under /usr, but then what I read about /usr talks about program files, not data files, which makes that sound incorrect as well. Everything I'm reading seems to take the approach that files should be in the home directory of the user who owns them, but that would leave them scattered about on the system, not where everyone can easily find them.
I may be over-analyzing the whole thing, but I would appreciate the input of those more experienced.
Offline
I'd put all the data on a separate partition or in an LVM container and then mount it (eg /mnt/filestore). Now you can create symlinks for whomever to wherever.
Offline
There was a thread with a similar goal not too long ago: http://bbs.archlinux.org/viewtopic.php?id=87125. Unfortunately, no concensus was reached.
For what it's worth, my preference is still /home/share.
Offline
I can see why no consensus was reached. I've now looked at that link, where some recommend a place in /usr, but the FSH info that I found says:
/usr is the second major section of the filesystem. /usr is shareable, read-only data
So that doesn't seem right.
Others recommend /var, but the FSH info says:
/var contains variable data files. This includes spool directories and files, administrative and logging data, and transient and temporary files.
Nope, not there either.
Final suggestion there is /home. The files don't need to belong to a particular user, as set forth previously, and the FHS helps with
/home is a fairly standard concept, but it is clearly a site-specific filesystem. The setup will differ from host to host. Therefore, no program should rely on this location.
For an OS that serves gazillions of files to as many users, it just strikes me as odd that there isn't a standard here. That being said, individuality is often a good thing.
Thank you for your suggestions, both of which make a lot of sense. I am leaning toward /home/share.
Offline
What's wrong with /srv ?
Offline
The reason I'm not sure this is the right place is that while the description sounds right
/srv contains site-specific data which is served by this system.
The information on the description sounds like it isn't
This main purpose of specifying this is so that users may find the location of the data files for particular service, and so that services which require a single tree for readonly data, writable data and scripts (such as cgi scripts) can be reasonably placed.
I'm not finding it right now, but the description talked about http, ftp, etc; I suppose samba fits there, just not sure. Again, maybe I'm overanalyzing this whole thing
Offline
/usr/share/?
[git] | [AURpkgs] | [arch-games]
Offline
I tend to use /var/$service with its own partition, ie /var/samba for the samba shares, /var/www for web stuff etc
Offline
What's wrong with /srv ?
+1
I use /srv divided by protocol or purpose:
/srv/http/
/srv/backup/
/srv/media/
/srv/samba/
/srv/ftp/
/srv/tftp/etc
I create symlinks where appropriate (eg, /srv/samba/backup --> /srv/backup/)
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline