Tim Soderstrom wrote:
Actually, I tend to symlink directories a lot and I don't really see the huge significant (I haven't read the entire thread - shame on me, I know). We use it at work frequently so that, for instance, we know where MySQL will always be (/var/lib/mysql) even if that is symlinked somewhere else (/mnt/san). When dealing with a lot of servers, it's nice to know where places are always going to be without having to take an extra step of looking up, say, the datadir. Simply things like adding up the size of the datadir just become easier when the datadir is generally always in the same place.
Same here. We have a /dealnews dir that all that stuff lives in. But, as disk space gets slim on a box, we may add an external SATA enclosure and make some symlinks. Keeps everything nice and neat.
In terms of performance, is a symlink really that big of a deal? You follow it once, cache the inode and call it done. I think the benefit of having symlinks outweighs the consequences.
Document it and be done. Those that find it important will make sure they don't use them.
On a production box, we would not have a symlink in this situation. But, I would like the option if I needed it.
-- Brian Moon Senior Web Engineer ------------------------------ When you care enough to spend the very least. http://dealnews.com/ _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
