Package: anacron
Version: 2.3-27
Severity: normal
Hello,
I noticed that anacron sets an environment (for running cron.daily jobs,
but probably even weekly and monthly jobs...) where the "logname" command
fails.
I mean: if a cron.daily job invokes the "logname" command, then this
command fails, thus producing the following error message on stderr:
logname: no login name
The error message (if not caught) is sent via local mail along with
the rest of the cron.daily job output.
It seems that this happens only when anacron is in charge of running
cron.{daily|weekly|monthly} jobs. Without anacron installed, cron
takes care of those jobs, and the "logname" command does not fail.
I think anacron should set an environment where the "logname" command
succeeds.
Thanks for your time!
Bye.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages anacron depends on:
ii debianutils 4.8.6
ii libc6 2.28-2
ii lsb-base 10.2018112800
Versions of packages anacron recommends:
ii cron [cron-daemon] 3.0pl1-130
ii rsyslog [system-log-daemon] 8.40.0-1
Versions of packages anacron suggests:
ii exim4-daemon-light [mail-transport-agent] 4.91-9
pn powermgmt-base <none>
-- no debconf information
