On Thu, 10 May 2007 12:30:27 +0000 Ferris McCormick <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-05-10 at 15:10 +0300, Daniel Iliev wrote: > > On Thu, 10 May 2007 11:45:23 +0100 > > "Clemente Aguiar" <[EMAIL PROTECTED]> wrote: > > > > > > > > I noticed that since the last upgrade (to mysql-5.0.38) that the > > > bin logging is being done to a different directory and with a > > > different name structure. > > > > > > 1. All log-bin files used to be in the /var/lib/mysql and used to > > > be the name of the host machine followed by -bin.xxxx. > > > > > > 2. Now, in this version (mysql-5.0.38) the logs are going to > > > /var/run/mysqld and with mysqld-bin.xxxxx names. > > > > > > The manual for version 5.0 > > > (http://dev.mysql.com/doc/refman/5.0/en/binary-log.html) says > > > that it should be as it was before (as in 1. above)! > > > > > > Anybody know why this is happening? > > > > > > Clemente > > > > > > Hah! Nice warning! > > If it works like this for me I'll pass the. Since I have several > > scripts depending on those paths and file names, this behavior would > > introduce breakage in my case. So, thanks for the just-in-time note > > - I had this update scheduled for tomorrow, after the "End Of Day" > > procedure. > > > > > > -- > > Best regards, > > Daniel > You mean like this. :) (From sparc.) > > mysql mysql 1607 2007-05-08 11:02 /var/run/mysqld/mysqld-bin.000001 > Oh! I thought this version has a hard-coded path and name. If I have the option "--log-bin[=base_name]" everything should be fine. Thanks for the examples! -- Best regards, Daniel -- [EMAIL PROTECTED] mailing list
