tag 543895 -moreinfo +confirmed +pending thanks Hi Peter,
On 01/-10/-28163 08:59 PM, Peter Rabbitson wrote:
> Javier Fernández-Sanguino Peña wrote:
>> On this bug, if you see cron's init.d script you will see this:
>>
>> ------------------------------------------------------------
>> parse_environment ()
>> {
>> ENV_FILE="none"
>> [ -r /etc/environment ] && ENV_FILE="/etc/environment"
>> [ -r /etc/default/locale ] && ENV_FILE="/etc/default/locale"
>>
>> (... parsing of variables ..)
>> }
>> ------------------------------------------------------------
>>
>> So, actually, cron will use the environment as defined in /etc/environment
>> or in /etc/default/locale, with the latter one taking precedence.
>>
>
> So you mean for things to work I actually need to delete /etc/environment?
> I am not sure what created it initially, but it has been sitting on my
> system with 0-length for a while. Maybe the script needs to check the file
> contents in addition to its existence?
I only realized what the actual bug was just after committing a fix for
the issue I first suspected.
Javier was right regarding the init script, but that's not why you're
seeing this bug. You're seeing it because cron's PAM config does not
parse /etc/default/locale.
A fix for the PAM issue has been committed, and is pending upload. Also,
the init script will now warn that if both /etc/environment and
/etc/default/locale contain locale information, those of
/etc/environment will be ignored (this was the original fix I had in mind).
Christian
signature.asc
Description: OpenPGP digital signature
