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.
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.
$0.02
Tim
On Oct 20, 2008, at 7:45 PM, Koa McCullough wrote:
I agree with Jeremy. It may be a bad practice to symlink dirs for
mysql
but if you run into a situation where you need it (ie. you've filled
up
the disk on a box and you plan to limp along with a new volume that is
symlinked into the data dir till new hardware can be stood up to
replace
it) it would really be frustrating to not have it. A better solution
might be to have a global sql variable ALLOW_SYMLINKS that is set to
'off' by default. At least that way it could be turned on without a
re-compile of Drizzle. Thoughts?
--Koa
On Mon, 2008-10-20 at 10:46 -0700, Jeremy Zawodny wrote:
I think it's still incredibly useful to be able to move stuff around
with symlinks.
Until we're all runnning ZFS by default, I think the transparency of
MyISAM's data storage (and other engines that do the same) is greatly
appreciated in times of space crisis, data migration, and so on.
That said, I wouldn't try to convince anyone to make a *new* engine
symlink friendly if it takes much extra effort.
Jeremy
On 10/19/08, Brian Aker <[EMAIL PROTECTED]> wrote:
Hi!
Historically folks have been able to control the directory of
datafiles and indexfiles for MyISAM. They have also been able
to "symlink" file around in the directories. Now this has
opened up a can of worms in the past, but the security issues
around it have not come up in recent time.
Seeing how modern disks are configured is this something we
should be supporting in the future? Does it still make sense?
I am leaning toward "no" but it would be nice to hear from
deployment folks if this matters.
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
