Bug#459344: /etc/cron.daily/apt exits with return code 1, despite being configured to do nothing
It doesn't appear to be the case that the cron script is actually doing any
updating by default.
I think this bug boils down to this: The apt cron script conflicts with an
already running apt (or aptitude) process. If the user is running apt, this
situation is not at all an error, the cron script just chose an inconvenient
time to be run. If the default behaviour is for the cron script to run, the
script should not just blindly report an error and exit 1, as the reports
that generates are confusing for users. (Sure made me wonder what the hell
And what kind of elitist garbage is it to then tell your legitimately confused
users to go read a book and fix the problem-by-default themselves?
That's my take on it.
Lord of, St. Luke Valor wrote (Sat, 12 Jan 2008):
> It only takes one hand to type. Fix it once, fix it for free, fix it for
> everyone, fix it forever. Have fun while you're at it.
> On 1/9/08, Francesco Poli <email@example.com> wrote:
> > On Tue, 8 Jan 2008 12:21:51 -0500 Lord of, St. Luke Valor wrote:
> > > I have a suggestion.
> > >
> > > 1) Find any text you are able on UNIX
> > > 2) Read about cron
> > >
> > > It is possible that cron was implemented in such a way that it must be
> > set
> > > to task. If the Anacron message bothers you, I would remove APT from
> > > the cron process. It will free up memory.
> > I *can* fix the issue for *my system*, but I would rather see the
> > *Debian package* fixed, so that other users will benefit from the fix...
> > After all, this is what the BTS is about: helping Debian to improve so
> > that users won't need to fix every single system by hand. Right?