More than three years without any (visible) action ... I was also hit by this problem with an own cron script. On a 24/7 server (without anacron) everything works fine, on some workstation (with anacron) the script breaks because it needs $HOME to access the GPG keyring. This means that the installation of anacron breaks scripts that work in a cron-environment.
Why can't anacron provide the same environment as cron does? Do you think that breaking otherwise working scripts (in a cron environment) justifies raising the bug's severity? Occassionally I see files like /.rnd. Such files might(!) be another manifestation of this problem (though I don't know which program accesses $HOME/.rnd). Note also that mails from cron have X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/root> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=root> I think adding the same headers for anacron mails would be very useful, too. Joachim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
