It just gives me the willies due to a bad experience I had when trying to resize /var not long ago. (See my message to Adam.) As long as the MySQL is in a separate actual file system it shouldn't be too bad. If /var is one file system, I don't like even the suggestion that if, say, syslogd filled up /var it could have bad consequences for my database.
In other word, paranoia. Jon <snip> On Wed, 2005-05-18 at 15:25 -0400, Jon Brock wrote: > MySQL, which defaults to placing its databases on /var (which I > consider a Bad Idea, but that's beside the point) Why is this bad? </snip> ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
