1 |
On Thu, 10 May 2007 12:30:27 +0000 |
2 |
Ferris McCormick <fmccor@g.o> wrote: |
3 |
|
4 |
> On Thu, 2007-05-10 at 15:10 +0300, Daniel Iliev wrote: |
5 |
> > On Thu, 10 May 2007 11:45:23 +0100 |
6 |
> > "Clemente Aguiar" <clemente.aguiar@××××××××××××××××.pt> wrote: |
7 |
> > |
8 |
> > > |
9 |
> > > I noticed that since the last upgrade (to mysql-5.0.38) that the |
10 |
> > > bin logging is being done to a different directory and with a |
11 |
> > > different name structure. |
12 |
> > > |
13 |
> > > 1. All log-bin files used to be in the /var/lib/mysql and used to |
14 |
> > > be the name of the host machine followed by -bin.xxxx. |
15 |
> > > |
16 |
> > > 2. Now, in this version (mysql-5.0.38) the logs are going to |
17 |
> > > /var/run/mysqld and with mysqld-bin.xxxxx names. |
18 |
> > > |
19 |
> > > The manual for version 5.0 |
20 |
> > > (http://dev.mysql.com/doc/refman/5.0/en/binary-log.html) says |
21 |
> > > that it should be as it was before (as in 1. above)! |
22 |
> > > |
23 |
> > > Anybody know why this is happening? |
24 |
> > > |
25 |
> > > Clemente |
26 |
> > |
27 |
> > |
28 |
> > Hah! Nice warning! |
29 |
> > If it works like this for me I'll pass the. Since I have several |
30 |
> > scripts depending on those paths and file names, this behavior would |
31 |
> > introduce breakage in my case. So, thanks for the just-in-time note |
32 |
> > - I had this update scheduled for tomorrow, after the "End Of Day" |
33 |
> > procedure. |
34 |
> > |
35 |
> > |
36 |
> > -- |
37 |
> > Best regards, |
38 |
> > Daniel |
39 |
> You mean like this. :) (From sparc.) |
40 |
> |
41 |
> mysql mysql 1607 2007-05-08 11:02 /var/run/mysqld/mysqld-bin.000001 |
42 |
> |
43 |
|
44 |
|
45 |
Oh! I thought this version has a hard-coded path and name. If I have |
46 |
the option "--log-bin[=base_name]" everything should be fine. |
47 |
|
48 |
Thanks for the examples! |
49 |
|
50 |
-- |
51 |
Best regards, |
52 |
Daniel |
53 |
|
54 |
-- |
55 |
gentoo-amd64@g.o mailing list |