kill -s SIGTERM on mysqld re-spawns another mysqld.
kill -s SIGTERM on mysqld re-spawns another mysqld.
I have a IA 64 machine with Redhat Hat Advanced server 4 (update 1) OS on it.
I have following mysql rpms this system.
mod_auth_mysql-2.6.1-2.2
libdbi-dbd-mysql-0.6.5-10.RHEL4.1
mysqlclient10-3.23.58-4.RHEL4.1
php-mysql-4.3.9-3.2
mysql-4.1.7-5.RHEL4.1
mysql-devel-4.1.7-5.RHEL4.1
mysql-bench-4.1.7-5.RHEL4.1
mysql-server-4.1.7-5.RHEL4.1
1.created a volume group and mounted this volume group on this system.
2.started mysqld_safe using the data directory that is present on the mount directory.
3. mysqld started with some pid "pid".we are not using the default pid file. we are creating the pid file in
different directory.
4.we have our own customised script to stop mysqld , which reads the pid file and passes the kill SIGTERM to that pid as below,
"kill -s SIGTERM pid".
but this command will stop the current mysqld but respawns one more "mysqld" with another pid.
( I am not using mysqladmin --shutdown because of some restrictions and also i have not creted any databased or i don't have any client connection also )
This behaviour will affect our application as our application is trying to umount the mount directory but fails to do so ,
becauase the new "myslqd" daemon is accessing this directory.
Is there any workaround for this problem.
MY requirement is
1.when I issue kill -s SIGTERM to the pid of mysqld , it should not re-spawn another mysqld.
2.I want to avoid re-spawing of mysqld.
Subject
Written By
Posted
kill -s SIGTERM on mysqld re-spawns another mysqld.
June 10, 2005 01:31AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.