On 12/30/2010 5:00 PM, Daevid Vincent wrote:
> Comment WHAT lines?
>
> I looked through /etc/init.d/mysql and don't see anything related to
> "check" or "chk". I eyeballed each line in the file and nothing stands out
> as the culprit causing an integrity check of the databases.
>
> developer@mypse:/etc/init.d$ ps aux | grep mysql
> 46:root 10239 0.0 0.1 1680 520 ? S Dec25 0:00 /bin/sh
> /usr/bin/mysqld_safe
> 49:mysql 11165 0.0 5.4 129924 27864 ? Sl Dec25 0:58
> /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql
> --pid-file=/var/run/mysqld/mysqld.pid --skip-external-locking --port=3306
> --socket=/var/run/mysqld/mysqld.sock
> 50:root 11167 0.0 0.1 2920 692 ? S Dec25 0:00 logger
> -p daemon.err -t mysqld_safe -i -t mysqld
> 81:1000 19149 0.0 0.1 3004 788 pts/0 R+ 21:54 0:00 grep -n
> -i --color=auto mysql
>
> <mailto:developer@mypse:/etc/init.d$> developer@mypse:/etc/init.d$ cat
> /proc/11165/cmdline
> /usr/sbin/mysqld--basedir=/usr--datadir=/var/lib/mysql--user=mysql--pid-fil
> e=/var/run/mysqld/mysqld.pid--skip-external-locking--port=3306--socket=/var
> /run/mysqld/mysqld.sockd
>
> Does anyone know if a "kill -SIGHUP 11165" will cause a reload of the
> configuration?
>
>
It won't reload the configuration.
http://dev.mysql.com/doc/refman/5.1/en/server-signal-response.html
Are you sure you aren't seeing the results of a dirty shutdown and
auto-recovery?
--
Shawn Green
MySQL Principal Technical Support Engineer
Oracle USA, Inc.
Office: Blountville, TN
