On Sat, Mar 9, 2013 at 12:21 AM, Steven Chamberlain <ste...@pyro.eu.org>wrote:
> On 08/03/13 17:37, Arturo Moral wrote:
> > [...] I should see a log
> > file inside /var/log/unattended-upgrades/ with details on every day's
> > check [...]
>
> I agree. On a wheezy/sid system using regular cron (not anacron) I get
> exactly this each day from unattended-upgrades 0.79.4 when there are no
> updates to install:
>
> /var/log/unattended-upgrades/unattended-upgrades.log :
> > 2013-03-08 06:26:39,208 INFO Initial blacklisted packages:
> > 2013-03-08 06:26:39,225 INFO Starting unattended upgrades script
> > 2013-03-08 06:26:39,225 INFO Allowed origins are: ['o=Debian,a=testing',
> 'origin=Debian,archive=testing,label=Debian-Security']
> > 2013-03-08 06:26:41,758 INFO No packages found that can be upgraded
> unattended
>
> In addition, I get a separate dpkg log only if there were any packages
> to actually update.
>
>
> I don't think your issue is due to configuration, but here is mine
> anyway for reference:
>
> /etc/apt/apt.conf.d/02periodic :
> > APT::Periodic::Enable "1";
> > APT::Periodic::Unattended-Upgrade "1";
> > APT::Periodic::AutocleanInterval "1";
> > APT::Periodic::Update-Package-Lists "1";
> > // I already 'randomise' the hour/minute of cron.daily on my hosts
> > APT::Periodic::RandomSleep "60";
>
My "Periodic" configuration parameters live under
"/etc/apt/apt.conf.d/20auto-upgrades", which was created by
unattended-upgrades on installation, but I don't think that this affects
the way they work.
>
> /etc/apt/apt.conf.d/50unattended-upgrades :
> > Unattended-Upgrade::Origins-Pattern {
> > "o=Debian,a=testing";
> > "origin=Debian,archive=testing,label=Debian-Security";
> > };
> > Unattended-Upgrade::Package-Blacklist {
> > };
> > Unattended-Upgrade::Mail "root@localhost";
>
> Regards,
> --
> Steven Chamberlain
> ste...@pyro.eu.org
>
