On Mon, 13 Oct 2003, Jake McHenry wrote:
> I woke up this morning to emails and phone calls. I didn't change
> anything dealing with the mysql server over the weekend, but it wasn't
> running this morning.There shouldn't be a reason why this process
> would go down and stay down.
>
> Here is the mysql file in logrotate.d.. Why is it trying to kill the
> process before and after rotation? Shouldn't this file be trying to
> restart the process after the rotation?
"kill -HUP" is not fatal if the program being signaled is set up to handle
it (which mysqld is). It should just go through some internal resetting
(rereading configs, reopening log files, etc.). This is how logrotate
gets mysqld to stop writing to the rotated logs and start writing to fresh
logs.
Not sure why things die, but it probably doesn't have to do with
logrotate.
>
>
>
> /var/log/mysqld.log {
> missingok
> create 0640 mysql mysql
> prerotate
> [ -e /var/lock/subsys/mysqld ] && /bin/kill -HUP `cat
> /var/run/mysqld/mysqld.pid 2> /dev/null ` || /bin/true
> endscript
> postrotate
> [ -e /var/lock/subsys/mysqld ] && /bin/kill -HUP `cat
> /var/run/mysqld/mysqld.pid 2> /dev/null ` || /bin/true
> endscript
> }
>
> Jake McHenry
> Nittany Travel MIS Coordinator
> http://www.nittanytravel.com
>
>
>
--
Matthew Saltzman
Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs
--
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list
