Quoting walter harms <wha...@bfs.de>:
restart it with the same parameter on the command line and see what happens
the server support a verbos option (never used) perhaps it will tell
you more.
I can start mysqld direct from the command line and reproduce the
problem. I checked and it seems the verbose option only works in
conjunction with --help.
Playing around with a couple of tools that are installed on FreeBSD, I
ran via truss and ktrace to see if there was anything obvious before
the process dies but not really. In ktrace you can see that it gets as
far as deciding that the remote connection should not be allowed then
rapidly just dies:
78353 echo GIO fd 1 wrote 44 bytes
"You are not welcome to use mysqld from tau.
"
78353 echo RET writev 44/0x2c
78353 echo CALL sigprocmask(SIG_BLOCK,0x800638400,0x7fffffffebd0)
78353 echo RET sigprocmask 0
78353 echo CALL sigprocmask(SIG_SETMASK,0x800638410,0)
78353 echo RET sigprocmask 0
78353 echo CALL sigprocmask(SIG_BLOCK,0x800638400,0x7fffffffeb80)
78353 echo RET sigprocmask 0
78353 echo CALL sigprocmask(SIG_SETMASK,0x800638410,0)
78353 echo RET sigprocmask 0
78353 echo CALL exit(0)
Interesting also to see it exits with status 0 :S. What would be the
best tool to debug this further?
thanks Andy.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
