I've been checking:
Code:
/opt/zimbra/bin/zmstorectl
which seems to be the only script which controls mysql server start.

Anyway... I've noticed that when it's about to stop mysql server it first flushes dirty pages. What it's strange is:

Code:
${MYSQL} -e "slave stop; set global innodb_max_dirty_pages_pct=0;"
I'm concerned about:
Code:
slave stop
which only makes sense in a master/slave mysql replication setup, particularly in the slave server role.
1) Does Zimbra in any of their multiserver setup uses mysql replication and have mysql slave servers... so that it makes sense?
2) Does the
Code:
slave stop
makes sense in a master server role by itself because of... I don't know.. it forces somehow flush of dirty pages ???
3) Is it maybe obsolete code?

4) Finally
Code:
slave stop
will have to be renamed to:
Code:
stop slave
when Zimbra will use Mysql 5.6 or later according to MySQL :: MySQL 5.1 Reference Manual :: 13.4.2.8 STOP SLAVE Syntax.

Thank you for any info you can provide.