[debian-mysql] Bug#810968: Bug#810968: Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

[Lennart Weller]

On Mon, Mar 07, 2016 at 06:37:49PM +0400, Sergey Vojtovich wrote:
> Existence of pid-file is a sure sign that there's mysqld running, the only
> exception is mysqld crash. What do you think about skipping this check?
> 
> I'd also suggest to turn things around and check for pid-file first and then
> just run "MYADMIN flush-logs" allowing it to return error in case of failure.

Yep. Switched the order for this one. But mysqladmin does not return 1
when it fails to connect. Did some additional testing. For now I put it
back to the way it was in the original logrotate and just check if
stdout/stderr of the command is null.
This probably merits a second bug report.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logrotate.patch
Type: text/x-diff
Size: 973 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20160307/269e9c8e/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20160307/269e9c8e/attachment.sig>