Hello Sean
On 2005-03-03 sean finney wrote:
> On Thu, Mar 03, 2005 at 09:32:28AM +0100, Christian Hammers wrote:
> > We now have three choices:
> > - just do /etc/init.d/mysql stop and if the server is still running
> > afterwards it's bad luck
> > - stick with the current way of killing all mysqld
> > - improving the script to maybe first fetch the PID out of the .pid file,
> > then do /etc/init.d/mysql stop and after that check ps just for the pid.
> >
> > I'm for 3. - any volunteers for a proper patch? :)
>
> sure, but one question first. would it be okay to assume the pidfile
> is in /var/run/mysqld/mysqld.pid, or should we have to parse the
> output of /usr/bin/mysqld --print-defaults for the pidfile?
Let's stay flexible, take something like this:
$ /usr/sbin/mysqld --print-defaults \
| tr " " "\n" \
| grep -- --pid-file \
| cut -d= -f2
bye,
-christian-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
