On Wed, Nov 29, 2006 at 07:33:20PM +0100, Nico Golde wrote: > Hi, > Adam Cécile reported #400719[0] to the fetchmail package. > > The question is wheter a system wide daemon should care > about the system wide locale configurations or not.
I'd say yes, since if the daemon spits out messages (either error or logs) the admin will want it to use the system's locale. BTW, IIRC currently the system's wide locale is set only by the locales package and introduced in either /etc/default/locale (glibc 2.3.6-5 and later, which means etch or later) or /etc/environment (woody or earlier) by it's postinst. Only a few (in my system) init.d scripts read this one in. > Fetchmail currently does, we are not calling it with > LC_MESSAGES=C or something similar. But are you sourcing the system's locale or are you depending on the locale of the user *starting* fetchmail? > I can't find anything about this in the policy but to me it > doesnt make sense to use a locale if you dont want it for > some programs. Why would you *not* want a locale? If the program has l10n support and it provides messages (even in a non-interactive way) there's chances some users will benefit from the translated messages. > Since it would be also possible to adjust the settings with > LC_ALL=C in /etc/default/fetchmail I just closed the bug but > reopened it now cause I want to hear some other opinions. > What do you think what is the best way here? I suggest you introduce a variable in /etc/default/fetchmail named "USE_SYSTEM_LOCALE" and do that (source the system locale if it exists) if set to 'Y'. That's better than forcing users to introduce the system locale in every /etc/default/XXX file and it also makes it easier to switch a system's locale (no need to touch in many different /etc/default/ files, just the 'locale' itself). Set the default to whatever you feel comfortable with. Just my few cents. Regards Javier
signature.asc
Description: Digital signature
