Re: daemontools and mysqld

svstat /service/mysqld
/service/mysqld: up (pid 4849) 60 seconds

cat /home/mysql/data/localhost.pid
4858

ps aux|grep mysql
root      4848  0.0  0.1  1392  308 ?        S   
19:00   0:00 supervise mysqld
mysql     4849  0.2  8.0 57476 20684 ?       S   
19:00   0:00 /usr/local/mysql/
mysql     4850  0.0  8.0 57476 20684 ?       S   
19:00   0:00 /usr/local/mysql/
mysql     4851  0.0  8.0 57476 20684 ?       S   
19:00   0:00 /usr/local/mysql/
mysql     4852  0.0  8.0 57476 20684 ?       S   
19:00   0:00 /usr/local/mysql/
mysql     4853  0.0  8.0 57476 20684 ?       S   
19:00   0:00 /usr/local/mysql/
mysql     4854  0.0  8.0 57476 20684 ?       S   
19:00   0:00 /usr/local/mysql/
mysql     4855  0.0  8.0 57476 20684 ?       S   
19:00   0:00 /usr/local/mysql/
mysql     4856  0.0  8.0 57476 20684 ?       S   
19:00   0:00 /usr/local/mysql/
mysql     4857  0.0  8.0 57476 20684 ?       S   
19:00   0:00 /usr/local/mysql/
mysql     4858  0.0  8.0 57476 20684 ?       S   
19:00   0:00 /usr/local/mysql/

It appears that the pid daemontools recognizes is the
first in the series and the pid that mysql will
shutdown to is the last in the series.

Any suggestions?


Gary


--- Paul Jarc <[email protected]> wrote:

> "Gary C. New" <[email protected]> wrote:
> > From the MySQL Docs it appears it should interpret
> the
> > SIGTERM appropriatly.
> 
> Since it apparently isn't, look at what it's doing. 
> Run svstat to
> find the process ID of the service, use "ps p $PID"
> (or "ps -p $PID"
> on SysV-based systems) to verify that that process
> is mysqld, and then
> do a system call trace on that process ("strace -p
> $PID" on Linux,
> "truss -p $PID" on Solaris, "ktrace
> somethingorother" on BSD).
> 
> 
> paul
>