Re: MySQL + external locking ...
This isn't a Debian issue but a quick fix it to put
enable-locking in /etc/mysql/my.cnf in place of
MySQL disables locking by default on Linux systems due to
supposed problems with threads and locking. However this
was a few years back and as far as I know, it hasn't been
tested since. I use enable-locking here doing around 15
queries per second and it hasn't failed yet.
On Sun, Nov 05, 2000 at 12:20:17AM -0500, Terry Katz wrote:
> I've been trying to get MySQL set up in a shared file system environment..
> It has a option 'skip locking' which disables external locking, when run on
> only a single machine.. I obviously don't want skip locking enabled, as I
> want the external locking.. For some reason, I've been having problems
> trying to 'disable' the skip locking feature ..
> I noticed the 'skip-locking' parameter in the my.cf file, and removed it
> .. started up mysql, issued 'show variables', and found it still ON .. I
> then did some poking around and found that the --skip-locking parameter was
> issued as well in the safe_mysqld start script .. I removed all occurances..
> stopped then started the server .. and its still ON!! I even looked through
> the Debian source and didn't find any default options for it being in (maybe
> I missed something??)
> Anyone have any insight??
> I would tend to think that the skip locking behavior, by default, should
> be turned off (which is whats lead on by the documentation).. as it can be
> dangerous when someone thinks it is turned off (like me:p) especially when
> all config options say it should be off...
> To UNSUBSCRIBE, email to firstname.lastname@example.org
> with a subject of "unsubscribe". Trouble? Contact email@example.com
Shane Wegner: firstname.lastname@example.org
A0ED DAC4 77EC D674 5487
5B5C 4F89 9A4E FFE3 035D