Hi Sean, On Wed, May 31, 2006 at 11:04:01AM -0400, sean finney wrote: > hi stella, > > On Wed, May 31, 2006 at 02:17:00PM +0100, Stella Power wrote: > > ++ nohup /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql > > --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-locking > > --port=3306 --socket=/var/run/mysqld/mysqld.sock > > this is what i want to see: > > ltrace /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql > --pid-file=/var/run/mysqld/mysqld.pid --skip-locking --port=3306 > --socket=/var/run/mysqld/mysqld.sock Ok I've started this running, will send on the trace once it completes. It'll probably take a while. > > it's interesting that 'ltrace mysqld' leads to the server running, so > i wonder if it's one of the above cmdline arguments causing the crash... No it doesn't cause the server to run, it just causes it to start very very slowly because of the tracing. As soon as I cancel the ltrace process, mysqld itself crashes in the same way. I think it's just that ltrace slows down mysqld sufficiently that the problem wasn't encountered during the 5mins I left ltrace running for. I'm going to leaving it running now and come back to in a few hours. Hopefully the output file won't be too large. > > > sean
Cheers, Stella -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
