/usr/sbin/anacron is a symlink to true

[Shalom Crown]

The original is present in /usr/sbin/anacron.distrib
Even when I change it , it changes back the next day during / after the anacron daily.

This is seen on 3 machines. They are all running Lubuntu live images, from USB DOKs, with casper-rw as a separate partition (not file).

On properly installed machines (mainly Xubuntu) there is no problem.

transspot@lubuntu:~$ ll /usr/sbin/anac*
lrwxrwxrwx 1 root root 9 Nov 19 12:54 /usr/sbin/anacron -> /bin/true*
-rwxr-xr-x 1 root root 30076 Dec 20 2012 /usr/sbin/anacron.distrib*

transspot@lubuntu:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.10
DISTRIB_CODENAME=saucy
DISTRIB_DESCRIPTION="Ubuntu 13.10"

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: anacron 2.3-19ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
CasperVersion: 1.336ubuntu1
Date: Mon Nov 25 09:29:30 2013
LiveMediaBuild: Lubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: anacron
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Uwe Lück (uwe-lueck)]

I have spent many days with learning about logrotate, cron jobs, and launchpad etiquette (as to posting a comment), which may take me into financial troubles. Now just let me …

I discovered this here starting from bug #1385537, and it helped me to fix the latter. However, I have described there how my situation differs from the situation here.

Another point: I have wondered and searched the web much time in order not only to find out how rotating logs and anacron etc. work, but actually: whether the developers of (Lu|Xu|U)buntu have *intended* to rotate logs by anacron.

Idea from that: Cron jobs might *intentionally* have been disabled (by linking to /bin/true) for a *live* session, maybe not thinking about the persistent case, rather about brief rescue or installation sessions where rotating and cron jobs seem to be useless and perhaps disturb jobs the user has in mind.