Thanks kewball for the excellent link.
It describes well what is the current status quo and what applications likely default to on Debian (And likely others especially in that branch). Most useful and informative
I do agree with you that /var can become the "Junk drawer
" on the system. That is why I posed the question as to using /srv for particular services thereby "naturally" relegating them to there own .. drawer.
Consider the Filesystem Hierarchy Standard
(Doc which is somewhat dated .... 2004). Particularly /srv : Data for services provided by this system
While to utilize the /srv mount point after the fact(Server Install) which would then require symlinks
, bind, or other options which may
open up its own "can of worms
", I was looking specifically for answers in using /srv from the "get go
" when first building the server. My apologies if that was not clear
If I may, please let me try to clarify a bit further:
In particular, I was looking for insight from LQ members into what concerns about or issues they may have run into when configuring a server to use /srv for sql DB, Web site and mail accounts, etc as opposed to using the "default" /var mount point for these services and data.
I guess it is really the "Admin's choice
" but I respect your/LQ input to help me make an informed decision.
Are there any "Gotch ya's" besides configuring the proper path during application install that one may need to look out for?
Any Admin/Security/Stability concerns?
All thoughts are welcome and I appreciate any and all help for this linux admin nooby.
Thanks again for your help and
all the best.