Kristian Kielhofner wrote: > Lonnie, > > Wow. I can honestly say that I never thought of this... Awesome! How > about this: > > 1) Add zoneinfo files from AstLinux 0.3 into /usr/share/zoneinfo (for > now). Eventually I would like to add a "build glibc zoneinfo" target > for the AstLinux devel environment. Shouldn't be too hard... > Agreed. We should limit this though bc the entire zoneinfo for the world is like 11MB. Perhaps we can come up with a way to only include certain time zones. > 2) Fix the TIMEZONE bug that you found. > > I don't see why we need the TIMEZONE_TZ variable. Usually apps use the > C library (uclibc in this case) to return the local time and date with > the proper offset to the current timezone. uClibc can do this. > Asterisk is different in that it has to support multiple timezones > (sometimes PER mailbox) in voicemail.conf. It reads /usr/share/zoneinfo > directly for this. You shouldn't need to set anything else up in the > rest of the system/Asterisk for this to work. I just confirmed that this does not work. uclibc does not use zoneinfo. It uses /etc/TZ. Here's how I tested.
I copied the /usr/share/zoneinfo/US/Central from CentOS to my build environment. I then entered the build environment as a chroot (chroot build_i586/root/ ). I copied /usr/share/zoneinfo/US/Central to /tmp/etc/localtime. The date command still showed UTC. So I copied that file to /tmp/etc/TZ. date still showed UTC. Deleted /tmp/etc/TZ, then created a new file with only the following line: CST5CDT. date then showed the correct value. Bottom line is we do need both /etc/localtime and /etc/TZ and their values are not the same. Therefore, we do need two variables. Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com _______________________________________________ Astlinux-users mailing list [email protected] http://lists.kriscompanies.com/mailman/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
