1 |
> -----Mensagem original----- |
2 |
> De: Ferris McCormick [mailto:fmccor@g.o] |
3 |
> Enviada: quinta-feira, 10 de Maio de 2007 13:34 |
4 |
> Para: gentoo-amd64@l.g.o |
5 |
> Assunto: Re: [gentoo-amd64] mysql log-bin dir |
6 |
> |
7 |
> |
8 |
> On Thu, 2007-05-10 at 15:10 +0300, Daniel Iliev wrote: |
9 |
> > On Thu, 10 May 2007 11:45:23 +0100 |
10 |
> > "Clemente Aguiar" <clemente.aguiar@××××××××××××××××.pt> wrote: |
11 |
> > |
12 |
> > > |
13 |
> > > I noticed that since the last upgrade (to mysql-5.0.38) |
14 |
> that the bin |
15 |
> > > logging is being done to a different directory and with a |
16 |
> different |
17 |
> > > name structure. |
18 |
> > > |
19 |
> > > 1. All log-bin files used to be in the /var/lib/mysql and |
20 |
> used to be |
21 |
> > > the name of the host machine followed by -bin.xxxx. |
22 |
> > > |
23 |
> > > 2. Now, in this version (mysql-5.0.38) the logs are going to |
24 |
> > > /var/run/mysqld and with mysqld-bin.xxxxx names. |
25 |
> > > |
26 |
> > > The manual for version 5.0 |
27 |
> > > (http://dev.mysql.com/doc/refman/5.0/en/binary-log.html) |
28 |
> says that |
29 |
> > > it should be as it was before (as in 1. above)! |
30 |
> > > |
31 |
> > > Anybody know why this is happening? |
32 |
> > > |
33 |
> > > Clemente |
34 |
> > |
35 |
> > |
36 |
> > Hah! Nice warning! |
37 |
> > If it works like this for me I'll pass the. Since I have several |
38 |
> > scripts depending on those paths and file names, this |
39 |
> behavior would |
40 |
> > introduce breakage in my case. So, thanks for the |
41 |
> just-in-time note - |
42 |
> > I had this update scheduled for tomorrow, after the "End Of Day" |
43 |
> > procedure. |
44 |
> > |
45 |
> > |
46 |
> > -- |
47 |
> > Best regards, |
48 |
> > Daniel |
49 |
> > |
50 |
> |
51 |
> You mean like this. :) (On sparc.) |
52 |
> mysql mysql 1607 2007-05-08 11:02 /var/run/mysqld/mysqld-bin.000001 |
53 |
> -- |
54 |
|
55 |
Yes like that. |
56 |
|
57 |
|
58 |
|
59 |
There is another behaviour which worries me, mysqld doesn't stop when I |
60 |
issue the following command: |
61 |
/etc/init.d/mysql stop |
62 |
* Stopping mysql ... OK |
63 |
* Stopping mysqld (0) ...[!!] |
64 |
|
65 |
The same thing happens when I reboot ... it takes forever, and when it |
66 |
comes up there is a warning saying that the mysqld.sock is present. |
67 |
|
68 |
Humm ... Worrying. |
69 |
|
70 |
Clemente |
71 |
-- |
72 |
gentoo-amd64@g.o mailing list |