Hi!
>>>>> "Peter" == Peter Zaitsev <[EMAIL PROTECTED]> writes:
Peter> Hello mysql,
Peter> It seems like you made an incomportable changes in 3.23.40 without
Peter> taking a time to write a release note :(
Peter> The mysql 3.23.39 used the system timezone by default:
Peter> maindb:/spylog/mysql/logs # date
Peter> Tue Aug 7 13:31:56 MSD 2001
Peter> | transaction_isolation | READ-COMMITTED
|
Peter> | timezone | MSD
|
Peter> | tmp_table_size | 4194304
Peter> Therefore MYSQL 3.23.40 does not determinate the timezone correctly:
Peter> |
Peter> | transaction_isolation | READ-COMMITTED
|
Peter> | timezone | Local time zone must be set--see�� manual
page
|
Peter> | tmp_table_size | 4194304
|
Are you sure you are not starting mysqld differently ?
According to my knowing, we have not changed anything in timezone
usage in MySQL.
The name if the timezone mysqld displays is what we get from the
following call:
{
struct tm tm_tmp;
localtime_r(&start_time,&tm_tmp);
strmov(time_zone,tzname[tm_tmp.tm_isdst == 1 ? 1 : 0]);
}
I don't know why localtime_r() doesn't work in your case, but I would guess
something in your setup that has changed.
The only way to affect the timezone is to set the TZ variable before
starting mysqld/safe_mysqld or by starting safe_mysqld with the
--timezone= option.
Peter> It uses GMT in this case which could dammage the data (as went in my
Peter> case)
Peter> The other thing is the manual does not contains much info about
Peter> setting timezone - only option to safe_mysqld which exports TZ
Peter> variable, which does not work:
Peter> root 19380 1 0 13:43 pts/8 00:00:00 sh
/usr/local/mysql/bin/safe_mysqld --mysqld=mysqld --user=mysql
--pid-file=/spylog/db/mysqld.pid --timezone=MSD --datadir=/spylog/db
Peter> It set's the timezone according to required value but date still bad:
Peter> | transaction_isolation | READ-COMMITTED
|
Peter> | timezone | MSD
|
Peter> | tmp_table_size | 4194304
mysql> select now();
Peter> +---------------------+
Peter> | now() |
Peter> +---------------------+
Peter> | 2001-08-07 09:44:44 |
Peter> +---------------------+
Peter> 1 row in set (0.00 sec)
Peter> Therefore date returns correct value.
Peter> rat:/spylog/layers # date
Peter> Tue Aug 7 13:47:05 MSD 2001
Peter> rat:/spylog/layers #
Peter> Do you have any ideas about this ? How I can fix the problem ?
Sorry, no ideas; It looks like there is some problem with your glibc
library.
Did you try the MySQL 3.23.39 and 3.23.40 binaries on the same
machine?
If not, then I think this is a glibc problem!
Regards,
Monty
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
