jcontonio wrote, circa 2007-03-26 4:49 PM: > Actually FreeBSD but you're exactly right. What's the best way to > solve this?
My FreeBSD knowledge isn't particularly keen so I probably can't be of much help, but it's entirely possible that you might not be able to adjust the inode count of a UFS volume without reformatting the volume or slice. You can't with ext3, either, as far as I'm aware. If you do have the luxury of being able to re-create the file system -- such as if /tmp is a file system all its own and you can move the data off of it, unmount it, reformat it, remount it, and move the data back all in a relatively short period of time with no services running -- then you could use the -i and -f options for /bin/newfs. Doing something like -f 1024 -i 1024 should give you a reasonably usable file system for doing file-system-based session store, but that's an awful lot of trouble to go to for what's basically provided as a lowest-common-denominator way to store session data My recommendation -- for this reason and for many, many others -- would be to switch to the ActiveRecord session store. Ideally, if you're using MySQL, use a MyISAM table (rather than InnoDB, which is a more advanced table format with transactions and other such features you don't need for an AR session store table). I suspect I'm not alone in recommending this, either, but if there are reasons you can't do so with your application I'd be interested in hearing them as there are other session store options available which might better meet your needs. Thanks, Jeff --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
