[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)

Sergey Vojtovich svoj at mariadb.org
Tue Mar 8 19:22:20 UTC 2016


Hi Lennart,

On Tue, Mar 08, 2016 at 04:25:06PM +0000, Lennart Weller wrote:
> March 8 2016 1:52 PM, "Sergey Vojtovich" <svoj at mariadb.org> wrote:
> > I adjusted your patch a bit, it seem to work well for me. Could you please
> > verify if you're fine with the attached version and it works for you too?
> 
> Well you basically dropped all the safe guards. But in the end its a logrotate script.
> Most people will never have the problem in the first place or know whatwent wrong on
> their end when they see your version of the script. So yeah fine with me.
Nice. So I'll apply this patch to upstream 10.0.

> 
> > You mean "$($MYADMIN flush-logs)" doesn't return 1? I just tested it on my side
> > and got exit status 1.
> 
> I'll try to find a reproducible bug some other time. But it can happen. EXIT_SUCCESS
> but error on stderr.
I went through relevant code and couldn't immediately find anything like that for
"flush-logs". But there's obvious exception for "ping": it may indeed return
success with "error on stderr".

Regards,
Sergey



More information about the pkg-mysql-maint mailing list