On 11/12/2023 06:12, Charles Curley wrote:
Sorry. I had already stopped the apt-daily-upgrade.timer, which
triggers the unattended upgrade service. (The couldn't give them
similar names to act as a mnemonic?) This refers to disabling the
unattended upgrade service.
I have not tested it, but fr
Dan Ritter wrote:
> Stefan Monnier wrote:
>> On my trusty Thinkpad X30, upgrades are sufficiently taxing that having
>> them run unexpectedly can be a real problem, so I tried to prevent
>> unattended upgrades a few months ago.
>
>
> I have always preferred the apticron package, which by default
>
On Sun, 10 Dec 2023 17:27:39 -0500
Greg Wooledge wrote:
> >
> > Thanks. I will disable as well.
>
> Disable *what*? Disabling a .service unit which is triggered by a
> timer event isn't going to stop it from running.
Sorry. I had already stopped the apt-daily-upgrade.timer, which
triggers t
On Sun, Dec 10, 2023 at 02:10:43PM -0700, Charles Curley wrote:
> On Sun, 10 Dec 2023 14:51:48 -0600
> David Wright wrote:
>
> > I think it might be worth googling and reading "three levels of off"
> > (with the quotes).
> >
> > 1. You can stop a service. That simply terminates the running
> >
On Sun, 10 Dec 2023 14:51:48 -0600
David Wright wrote:
> I think it might be worth googling and reading "three levels of off"
> (with the quotes).
>
> 1. You can stop a service. That simply terminates the running
> instance of the service and does little else. If due to some form
> o
Stefan Monnier wrote:
> On my trusty Thinkpad X30, upgrades are sufficiently taxing that having
> them run unexpectedly can be a real problem, so I tried to prevent
> unattended upgrades a few months ago.
I have always preferred the apticron package, which by default
updates daily and sends an e
On Sun 10 Dec 2023 at 13:39:50 (-0700), Charles Curley wrote:
> On Sun, 10 Dec 2023 14:17:36 -0600
> David Wright wrote:
>
> > Why is the service loaded, enabled and enabled then? Don't you need
> > to disable or mask it? Presumably it sits there, dead, all day
> > normally, and pops up at an app
On Sun, 10 Dec 2023 14:17:36 -0600
David Wright wrote:
> Why is the service loaded, enabled and enabled then? Don't you need
> to disable or mask it? Presumably it sits there, dead, all day
> normally, and pops up at an appropriate time.
As I understand things, start and stop are for immediate c
On Sun 10 Dec 2023 at 11:00:37 (-0700), Charles Curley wrote:
> On Sun, 10 Dec 2023 16:11:44 +
> Michael Kjörling <2695bd53d...@ewoof.net> wrote:
>
> > On 10 Dec 2023 08:49 -0700, from charlescur...@charlescurley.com
> > (Charles Curley): [...]
> >
> > Exactly how did you "shut down" unatte
On Sun, 10 Dec 2023 23:59:04 +0700
Max Nikulin wrote:
> On 10/12/2023 22:49, Charles Curley wrote:
> [...]
>
> systemctl status apt-daily-upgrade.timer
>
root@issola:~# systemctl status apt-daily-upgrade.timer
● apt-daily-upgrade.timer - Daily apt upgrade and clean activities
Loaded: l
On Sun, 10 Dec 2023 16:11:44 +
Michael Kjörling <2695bd53d...@ewoof.net> wrote:
> On 10 Dec 2023 08:49 -0700, from charlescur...@charlescurley.com
> (Charles Curley): [...]
>
> Exactly how did you "shut down" unattended-upgrades?
>
root@chaffee:/etc/dhcp# systemctl stop unattended-upgrade
> I double checked this morning. All machines had unattended upgrades
> shut off as of yesterday evening, well before the
> unattended-uogrades ran.
On my trusty Thinkpad X30, upgrades are sufficiently taxing that having
them run unexpectedly can be a real problem, so I tried to prevent
unattende
On 10/12/2023 22:49, Charles Curley wrote:
root@issola:/var# systemctl status unattended-upgrades.service
systemctl status apt-daily-upgrade.timer
On 10 Dec 2023 08:49 -0700, from charlescur...@charlescurley.com (Charles
Curley):
> Due to the recent traffic about the defective kernel in Bookworm
> (12.3), I shut down unattended-upgrades on all my machines (Bookworm
> and Bullseye). To my surprise, three of them ran unattended-upgrades
> anyw
On Tue, 15 Oct 2019 17:03:19 +1100
Keith Bainbridge wrote:
> Also, there is a process to get one PC to download the updates, and
> share that /var/cache/apt/archives/ to your other PCs
You might look into apt-cacher or apt-cacher-ng for that.
--
Does anybody read signatures any more?
https:
Le 15/10/2019 à 14:10, Curt a écrit :
On 2019-10-15, Yvan Masson wrote:
I am currently using a VM with snapshots to try to find the culprit, I
will let you know.
I could not find the culprit so I reported the bug:
https://github.com/mvo5/unattended-upgrades/issues/229
There's this (not s
On 2019-10-15, Yvan Masson wrote:
>>
>> I am currently using a VM with snapshots to try to find the culprit, I
>> will let you know.
>
> I could not find the culprit so I reported the bug:
> https://github.com/mvo5/unattended-upgrades/issues/229
>>>
There's this (not sure if it's your issue or
Le 15/10/2019 à 09:19, Yvan Masson a écrit :
Le 15/10/2019 à 08:03, Keith Bainbridge a écrit :
On 15/10/19 11:31 am, Keith Bainbridge wrote:
How to prevent a repeat is the real question. My only suggestion is
extend the time-out, but how long. Maybe run manual upgrades on one
machine every
Le 15/10/2019 à 08:03, Keith Bainbridge a écrit :
On 15/10/19 11:31 am, Keith Bainbridge wrote:
How to prevent a repeat is the real question. My only suggestion is
extend the time-out, but how long. Maybe run manual upgrades on one
machine every day, before shutting down the others??
Ther
On 15/10/19 11:31 am, Keith Bainbridge wrote:
How to prevent a repeat is the real question. My only suggestion is
extend the time-out, but how long. Maybe run manual upgrades on one
machine every day, before shutting down the others??
There was a response suggesting getting cron to run som
On Tue, 15 Oct 2019 11:31:22 +1100
Keith Bainbridge wrote:
> It was intuition rather than any knowledge I had - beyond the fact
> that sometimes upgrade takes longer than normal.
>
> How to prevent a repeat is the real question.
Upgrades and updates often require fetching across the network, wh
On 14/10/19 7:42 pm, Yvan Masson wrote:
You were right Keith: after applying some updates manually, remaining
updates are
properly installed with unattended-upgrade… Now I need to understand
what was
blocking.
It was intuition rather than any knowledge I had - beyond the fact that
sometim
Le 14/10/2019 à 04:22, Keith Bainbridge a écrit :
On 14/10/19 6:16 am, Yvan Masson wrote:
Hi,
I forgot to tell that I configured another important thing, in
/etc/systemd/logind.conf:
…
InhibitDelayMaxSec=600
…
Which should let enough time to do the upgrades.
Any hint is very welcome!
Le 12
On 14/10/19 6:16 am, Yvan Masson wrote:
Hi,
I forgot to tell that I configured another important thing, in
/etc/systemd/logind.conf:
…
InhibitDelayMaxSec=600
…
Which should let enough time to do the upgrades.
Any hint is very welcome!
Le 12/10/2019 à 18:45, Yvan Masson a écrit :
Hi list,
Hi,
I forgot to tell that I configured another important thing, in
/etc/systemd/logind.conf:
…
InhibitDelayMaxSec=600
…
Which should let enough time to do the upgrades.
Any hint is very welcome!
Le 12/10/2019 à 18:45, Yvan Masson a écrit :
Hi list,
I configured some Buster desktops in a sc
Hi,
looks like the culprit is a /etc/cron.daily/do-agent cron-job which
executes the /opt/digitalocean/do-agent/scripts/update.sh script which
includes following if statement:
if command -v apt-get 2&>/dev/null; then
apt-get -qq update -o
Dir::Etc::sourcelist="sources.list
> I did some further debugging and it is the
> /usr/lib/apt/apt.systemd.daily script executed by apt-daily systemd
> service unit which updates the package index from the sources:
I configured cron with one minute interval to log the output of "apt
policy" with a timestamp into a log file in order
> Looks like the "apt update" or equivalent ran by unattended-upgrades
> ignored the /etc/apt/sources.list file and used only
> /etc/apt/sources.list.d/digitalocean-agent.list as a source for
> repositories.
> What might cause this behavior?
I did some further debugging and it is the
/usr/lib/apt/
On Tue, 16 Oct 2018 07:42:56 +0200
john doe wrote:
Hello john,
>I'll never understand why being so drastic is a good idea when you can
>simply disable it:
Combinations of the following come to mind. Could well be more. No
doubt, you and others can come up with reasons to keep it. We all mak
On 10/16/2018 8:35 AM, likcoras wrote:
> On 10/16/18 2:42 PM, john doe wrote:
>> On 10/16/2018 7:23 AM, Tixy wrote:
>>> On Mon, 2018-10-15 at 21:54 +0100, Brian wrote:
On Mon 15 Oct 2018 at 17:45:36 -0300, rv riveravaldez wrote:
> 2. If the answer is 'yes': which would be the best/proper w
likcoras composed on 2018-10-16 15:35 (UTC+0900):
> john doe wrote:
>> I'll never understand why being so drastic is a good idea when you can
>> simply disable it:
>> https://wiki.debian.org/UnattendedUpgrades
>> "Below is an example /etc/apt/apt.conf.d/02periodic:
>> // Control parameters for
On 10/16/18 2:42 PM, john doe wrote:
On 10/16/2018 7:23 AM, Tixy wrote:
On Mon, 2018-10-15 at 21:54 +0100, Brian wrote:
On Mon 15 Oct 2018 at 17:45:36 -0300, rv riveravaldez wrote:
2. If the answer is 'yes': which would be the best/proper way to do
it?
apt purge unattended upgrades
I'll
On 10/16/2018 7:23 AM, Tixy wrote:
> On Mon, 2018-10-15 at 21:54 +0100, Brian wrote:
>> On Mon 15 Oct 2018 at 17:45:36 -0300, rv riveravaldez wrote:
>>
>>> Hi, two doubts:
>>>
>>> 1. Is it OK to disable/remove Unattended Upgrades on Debian
>>> testing?
>>
>> Of course it is; if that is what you wan
On Mon, 2018-10-15 at 21:54 +0100, Brian wrote:
> On Mon 15 Oct 2018 at 17:45:36 -0300, rv riveravaldez wrote:
>
> > Hi, two doubts:
> >
> > 1. Is it OK to disable/remove Unattended Upgrades on Debian
> > testing?
>
> Of course it is; if that is what you want.
>
> > 2. If the answer is 'yes': w
On 16/10/2018 09:45, rv riveravaldez wrote:
Hi, two doubts:
1. Is it OK to disable/remove Unattended Upgrades on Debian testing?
2. If the answer is 'yes': which would be the best/proper way to do it?
Thanks a lot!
I use systemctl to mask all the apt-daily units:
systemctl mask apt-daily-upgra
On Mon 15 Oct 2018 at 17:45:36 -0300, rv riveravaldez wrote:
> Hi, two doubts:
>
> 1. Is it OK to disable/remove Unattended Upgrades on Debian testing?
Of course it is; if that is what you want.
> 2. If the answer is 'yes': which would be the best/proper way to do it?
apt purge unattended upgr
On Tuesday 18 April 2017 15:55:25 Jonathan Dowland wrote:
> If you Lisi revisit this and it doesn't work, I could try to help.
Thanks, Jonathan. I may therefore revisit it later this week! :-)
Lisi
I've just had a look, and I didn't do anything particularly special: I
installed unattended-upgrades, ran dpkg-reconfigure -plow unattended-upgrades
which created the necessary file in /etc/apt/apt.conf.d, and it is working.
However, the default settings only do security updates; I have some packa
On Wednesday 05 April 2017 21:26:16 Erwan David wrote:
> Le 04/05/17 à 21:59, Tom Dial a écrit :
> > On 04/05/2017 10:22 AM, Lisi Reisz wrote:
> >> On Wednesday 05 April 2017 15:46:53 Jonathan Dowland wrote:
> >>> On Wed, Apr 05, 2017 at 10:26:18PM +0900, Mark Fletcher wrote:
> I am going to h
On Wednesday 05 April 2017 20:59:02 Tom Dial wrote:
> On 04/05/2017 10:22 AM, Lisi Reisz wrote:
> > On Wednesday 05 April 2017 15:46:53 Jonathan Dowland wrote:
> >> On Wed, Apr 05, 2017 at 10:26:18PM +0900, Mark Fletcher wrote:
> >>> I am going to have a go at getting unattended-upgrades to work so
Le 04/05/17 à 21:59, Tom Dial a écrit :
>
>
> On 04/05/2017 10:22 AM, Lisi Reisz wrote:
>> On Wednesday 05 April 2017 15:46:53 Jonathan Dowland wrote:
>>> On Wed, Apr 05, 2017 at 10:26:18PM +0900, Mark Fletcher wrote:
I am going to have a go at getting unattended-upgrades to work sometime
>>
On 04/05/2017 10:22 AM, Lisi Reisz wrote:
> On Wednesday 05 April 2017 15:46:53 Jonathan Dowland wrote:
>> On Wed, Apr 05, 2017 at 10:26:18PM +0900, Mark Fletcher wrote:
>>> I am going to have a go at getting unattended-upgrades to work sometime
>>> in the next few days, I will post back what my
On Wednesday 05 April 2017 15:46:53 Jonathan Dowland wrote:
> On Wed, Apr 05, 2017 at 10:26:18PM +0900, Mark Fletcher wrote:
> > I am going to have a go at getting unattended-upgrades to work sometime
> > in the next few days, I will post back what my results, even if the only
> > thing that result
On Wed, Apr 05, 2017 at 10:26:18PM +0900, Mark Fletcher wrote:
> I am going to have a go at getting unattended-upgrades to work sometime
> in the next few days, I will post back what my results, even if the only
> thing that results is sympathy for your situation and a "me-too!"
I have a working
I'm going to break my own self-imposed rule on top-posting to make sure
you see my exhortation not to cc me as I am subscribed to the list
On Wed, Apr 05, 2017 at 01:20:56AM +0100, Lisi Reisz wrote:
> On Tuesday 04 April 2017 20:29:26 Gregor Zattler wrote:
> > Hi Mark, debian users,
> >
> > * Mar
On Tuesday 04 April 2017 20:29:26 Gregor Zattler wrote:
> Hi Mark, debian users,
>
> * Mark Fletcher [2017-04-03; 21:08]:
> > On Sat, Apr 01, 2017 at 06:04:16PM +0200, Gregor Zattler wrote:
> > There's another thread recently (during March, I think) on this mailing
> > list about the same subject.
Hi Mark, debian users,
* Mark Fletcher [2017-04-03; 21:08]:
> On Sat, Apr 01, 2017 at 06:04:16PM +0200, Gregor Zattler wrote:
> There's another thread recently (during March, I think) on this mailing
> list about the same subject. The gyst is you need to do a
> dpkg-reconfigure unattended-upgrad
On Sat, Apr 01, 2017 at 06:04:16PM +0200, Gregor Zattler wrote:
> Hi Gregor,
>
> one more detail about the configuration of said system (see below/between):
>
> Any ideas how to proceed?
>
> Ciao; Gregor
>
>
There's another thread recently (during March, I think) on this mailing
list about t
Hi Gregor,
one more detail about the configuration of said system (see below/between):
Any ideas how to proceed?
Ciao; Gregor
* Gregor Zattler [2017-03-31; 17:34]:
> Dear fellow debian users,
>
> this is about a debian stable (=jessie) system and it does not
> upgrade unattended and I have n
On Friday 24 March 2017 17:34:58 Teemu Likonen wrote:
> Lisi Reisz [2017-03-24 17:13:21Z] wrote:
> > On Friday 24 March 2017 09:56:23 didier gaumet wrote:
> >> # dpkg-reconfigure -plow unattended-upgrades
> >
> > This is what I had missed! I have now run it.
>
> The command creates file /etc/apt/a
Lisi Reisz [2017-03-24 17:13:21Z] wrote:
> On Friday 24 March 2017 09:56:23 didier gaumet wrote:
>> # dpkg-reconfigure -plow unattended-upgrades
>
> This is what I had missed! I have now run it.
The command creates file /etc/apt/apt.conf.d/20auto-upgrades:
APT::Periodic::Update-Package-List
On Friday 24 March 2017 09:56:23 didier gaumet wrote:
> Le 24/03/2017 à 09:41, Lisi Reisz a écrit :
> [...]
>
> > Let's start with the file you mention:
> > /etc/apt/apt.conf.d/20auto-upgrades It isn't there.
>
> the Debian wiki indicates that it has to be created, either by typing a
> content in a
Le 24/03/2017 à 09:41, Lisi Reisz a écrit :
[...]
> Let's start with the file you mention: /etc/apt/apt.conf.d/20auto-upgrades
> It isn't there.
the Debian wiki indicates that it has to be created, either by typing a
content in an editor or you can symply type as root:
# dpkg-reconfigure -plow
On Thursday 23 March 2017 04:26:17 Teemu Likonen wrote:
> Lisi Reisz [2017-03-22 00:37:18Z] wrote:
> > How do I get unattended upgrades a) to function and b) to tell me when
> > it has upgraded something.
>
> Probably you need to add the following lines in the top of
> /etc/apt/apt.conf.d/50unatten
Thank you for your further response. I have tried to answer your questions,
which will show you that I am completely at sea.
On Thursday 23 March 2017 09:03:01 didier gaumet wrote:
> Le 23/03/2017 à 02:06, Lisi Reisz a écrit :
> > Thank you. Yes, I have read and tried to follow it. I quote:
>
Le 23/03/2017 à 02:06, Lisi Reisz a écrit :
>
> Thank you. Yes, I have read and tried to follow it. I quote:
> -
> To install these packages, run the following command as root:
>
> # apt-get install unattended-upgrades apt-listchanges
> The default configuration file for the unattended-
Lisi Reisz [2017-03-22 00:37:18Z] wrote:
> How do I get unattended upgrades a) to function and b) to tell me when
> it has upgraded something.
Probably you need to add the following lines in the top of
/etc/apt/apt.conf.d/50unattended-upgrades file (or some other file in
the same directory).
On Wednesday 22 March 2017 07:42:09 didier gaumet wrote:
> there is a doc in the Debian wiki:
> https://wiki.debian.org/UnattendedUpgrades
Thank you. Yes, I have read and tried to follow it. I quote:
-
To install these packages, run the following command as root:
# apt-get install unatt
there is a doc in the Debian wiki:
https://wiki.debian.org/UnattendedUpgrades
Can anyone help with this?
Just to be clear, after apache is upgraded via unattended-upgrades,
apache is in the stopped state. I have to manually start it again.
On 27/02/2017 12:45 PM, Yasir Assam wrote:
> Running Jessie. Every time apache is upgraded through
> unattended-upgrades, it isn't rest
On Thu, 9 Jun 2016 11:39:36 +0200, Wolfgang Karall
wrote:
>It's not unattended-upgrades, what you're seeing is the output of
>needrestart, which is configured by default to only showing what it
>would do, but not actually restarting anything.
>
>Take a look at the configuration below /etc/needres
Hello,
On 16-06-08 22:11:33, Jesper Dybdal wrote:
> At the end of unattended-upgrades-dpkg.log, I see:
>
> >Services to be restarted:
> >Skipping dbus.service...
> >systemctl restart apache2.service cron.service
> >Log ended: 2016-06-08 04:36:36
>
> However, apache2 and cron have not been resta
On 3/16/2015 10:53 PM, Seeker wrote:
On 3/16/2015 3:57 AM, Tapio Lehtonen wrote:
I can't understand how unattended upgrades continues to work after
Jessi is stable. In wheezy the config file has
"origin=Debian,archive=stable,label=Debian-Security";
"origin=Debian,archive=oldstable,l
On 3/16/2015 3:57 AM, Tapio Lehtonen wrote:
I can't understand how unattended upgrades continues to work after
Jessi is stable. In wheezy the config file has
"origin=Debian,archive=stable,label=Debian-Security";
"origin=Debian,archive=oldstable,label=Debian-Security";
I don't want to
On 19/02/2015 15:05, Marko Randjelovic wrote:
The best solution I see is to edit your /etc/cron.daily/apt and set
COLUMNS and LINES environment variables manualy, but since
/usr/lib/perl5/Term/ReadKey.pm belongs to libterm-readkey-perl
package, I would check if this package is installed and if
On Thu, 19 Feb 2015 08:41:33 +0200
Brent Clark wrote:
> Good day Guys
>
> I just installed and new to unattended-upgrades.
>
> Looking at the logs this morning I see the folllowing.
>
> cat
> /var/log/unattended-upgrades/unattended-upgrades-dpkg_2015-02-19_06\:48\:53.476190.log
>
>
> (Read
On Wednesday 22 October 2014 10:46:13 Paul van der Vlis wrote:
> op 19-10-14 14:46, Chris schreef:
> > Hi,
> >
> > I'm having no luck getting unattended-upgrads working on a Wheezy
> > server. The image for Wheezy is from my vServer provider and has not
> > been a problem until now. I'm not a prog
On Tuesday 21 October 2014 22:59:05 Andrei POPESCU wrote:
> On Ma, 21 oct 14, 22:45:20, Chris wrote:
> > $ls -lah |grep apt
> > -rw-r--r-- 1 root root 15K Sep 23 08:20 apt
>
> The script is not executable ;)
>
> Kind regards,
> Andrei
oh... I guess that was the problem. Is this a common pract
op 19-10-14 14:46, Chris schreef:
> Hi,
>
> I'm having no luck getting unattended-upgrads working on a Wheezy
> server. The image for Wheezy is from my vServer provider and has not
> been a problem until now. I'm not a programmer so bear with me.
>
> No entry appears in /var/log/unattended-upgrad
On Ma, 21 oct 14, 22:45:20, Chris wrote:
>
> $ls -lah |grep apt
> -rw-r--r-- 1 root root 15K Sep 23 08:20 apt
The script is not executable ;)
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.
On Monday 20 October 2014 20:58:48 Andrei POPESCU wrote:
> On Lu, 20 oct 14, 20:39:59, Chris wrote:
> > Yes, I do have anacron installed because I thought that might be the
> > problem.
>
> If you have anacron installed the jobs will be run by anacron, but you
> already have proven that daily cron
On Lu, 20 oct 14, 20:39:59, Chris wrote:
>
> Yes, I do have anacron installed because I thought that might be the problem.
If you have anacron installed the jobs will be run by anacron, but you
already have proven that daily cronjobs work, so that's probably a dead
end.
> How would you sugges
On Monday 20 October 2014 20:13:14 Andrei POPESCU wrote:
> On Lu, 20 oct 14, 17:48:35, Chris wrote:
> > No, that's not the problem.
> >
> > "No entry appears in /var/log/unattended-upgrades/unattended-upgrades.log
> > other than the dry runs."
> >
> > i.e. today on 20 October the last entry is st
On Lu, 20 oct 14, 17:48:35, Chris wrote:
>
> No, that's not the problem.
>
> "No entry appears in /var/log/unattended-upgrades/unattended-upgrades.log
> other than the dry runs."
>
> i.e. today on 20 October the last entry is still from yesterday:
>
> 2014-10-19 14:38:11,701 DEBUG pkgs that lo
On Sun, Oct 19, 2014 at 02:46:07PM +0200, Chris wrote:
> "origin=Debian,archive=stable,label=Debian-Security";
> Unattended-Upgrade::Origins-Pattern::
> "origin=Debian,archive=oldstable,label=Debian-Security";
^
Is that right?
--
"If you're not careful, the newsp
On Monday 20 October 2014 12:39:45 Andrei POPESCU wrote:
> On Du, 19 oct 14, 14:46:07, Chris wrote:
> > Hi,
> >
> > I'm having no luck getting unattended-upgrads working on a Wheezy server.
>
> ...
>
> > 2014-10-19 14:38:11,709 INFO No packages found that can be upgraded
> > unattended
>
> Seem
On Du, 19 oct 14, 14:46:07, Chris wrote:
> Hi,
>
> I'm having no luck getting unattended-upgrads working on a Wheezy server.
...
> 2014-10-19 14:38:11,709 INFO No packages found that can be upgraded unattended
Seems like there's nothing to upgrade.
Kind regards,
Andrei
--
http://wiki.debian.or
On Thu, Mar 7, 2013 at 5:35 PM, David Sastre Medina <
d.sastre.med...@gmail.com> wrote:
> On Thu, Mar 07, 2013 at 12:47:31PM +0100, A wrote:
> > On Thu, Mar 7, 2013 at 11:18 AM, David Sastre Medina <
> > d.sastre.med...@gmail.com> wrote:
> > >
> > > This is from /etc/cron.daily/apt:
> > >
> > > #
On Thu, Mar 07, 2013 at 12:47:31PM +0100, A wrote:
> On Thu, Mar 7, 2013 at 11:18 AM, David Sastre Medina <
> d.sastre.med...@gmail.com> wrote:
> >
> > This is from /etc/cron.daily/apt:
> >
> > # auto upgrade all upgradeable packages
> > UPGRADE_STAMP=/var/lib/apt/periodic/upgrade-stamp
> > if whic
On Thu, Mar 7, 2013 at 11:18 AM, David Sastre Medina <
d.sastre.med...@gmail.com> wrote:
> On Wed, Mar 06, 2013 at 11:34:33PM +0100, A wrote:
> > On Wed, Mar 6, 2013 at 9:03 PM, David Sastre Medina <
> > d.sastre.med...@gmail.com> wrote:
> >
> > > On Wed, Mar 06, 2013 at 08:32:47PM +0100, A wrote:
On Wed, Mar 06, 2013 at 11:34:33PM +0100, A wrote:
> On Wed, Mar 6, 2013 at 9:03 PM, David Sastre Medina <
> d.sastre.med...@gmail.com> wrote:
>
> > On Wed, Mar 06, 2013 at 08:32:47PM +0100, A wrote:
> > > Hola, David,
> > >
> > > The file exists under that path, but I can't confirm if it's runnin
On Wed, Mar 6, 2013 at 9:03 PM, David Sastre Medina <
d.sastre.med...@gmail.com> wrote:
> On Wed, Mar 06, 2013 at 08:32:47PM +0100, A wrote:
> > Hola, David,
> >
> > The file exists under that path, but I can't confirm if it's running
> since
> > 'invoke-rc.d unattended-upgrades status' returns no
On Wed, Mar 06, 2013 at 08:32:47PM +0100, A wrote:
> Hola, David,
>
> The file exists under that path, but I can't confirm if it's running since
> 'invoke-rc.d unattended-upgrades status' returns no output. The same for
> 'start' or 'stop' options, no output. I've checked that the proper symlinks
Hola, David,
The file exists under that path, but I can't confirm if it's running since
'invoke-rc.d unattended-upgrades status' returns no output. The same for
'start' or 'stop' options, no output. I've checked that the proper symlinks
to the file exist under "/etc/rc0.d" and "/etc/rc6.d".
In ad
On Tue, Mar 05, 2013 at 01:01:45PM +0100, A wrote:
> Hi there,
>
> I've been trying to make *unattended-upgrades* working on Wheezy with no
> success so far.
>
> The steps I have followed are:
>
> - Install *unattended-upgrades*
> - Enable it
>
> sudo dpkg-reconfigure -plow unattended
El 2011-01-05 a las 14:43 +, Tony van der Hoff escribió:
(resending to the list)
> On 05/01/11 12:50, Camaleón wrote:
>> If my findings are correct, the problem is in the script itself and the
>> package should be updated... but being for lenny (stable), I'm not sure
>> if that is possible.
>
On Tue, 04 Jan 2011 22:51:51 +0100, Simon Hollenbach wrote:
>> > Thanks for replying, Cameleon, but as I said, apt-get install just
>> > did it effortlessly. No interaction required.
>>
>> No prompts asking you about when using "apt-get upgrade"? Weird,
>> because that was what the log said and t
> > Thanks for replying, Cameleon, but as I said, apt-get install just did
> > it effortlessly. No interaction required.
>
> No prompts asking you about when using "apt-get upgrade"? Weird, because
> that was what the log said and the package gets blacklisted because of
> that :-?
>
Hi folks,
I
On Tue, 04 Jan 2011 17:34:40 +, Tony van der Hoff wrote:
> On 04/01/11 17:23, Camaleón wrote:
>>> 2011-01-04 16:13:26,586 DEBUG pkg 'phpmyadmin' has conffile prompt
>>> 2011-01-04 16:13:26,595 DEBUG blacklist: ['phpmyadmin']
>>
>> (...)
>>
>>> 2011-01-04 16:13:27,272 INFO No packages found th
On 04/01/11 17:23, Camaleón wrote:
On Tue, 04 Jan 2011 16:30:46 +, Tony van der Hoff wrote:
On 04/01/11 15:58, Camaleón wrote:
On Mon, 03 Jan 2011 17:54:37 +, Tony van der Hoff wrote:
Can anyone explain why this happens? Should I upgrade phpmyadmin
manually?
Maybe you can run the s
On Tue, 04 Jan 2011 16:30:46 +, Tony van der Hoff wrote:
> On 04/01/11 15:58, Camaleón wrote:
>> On Mon, 03 Jan 2011 17:54:37 +, Tony van der Hoff wrote:
>>
>>> Can anyone explain why this happens? Should I upgrade phpmyadmin
>>> manually?
>>
>> Maybe you can run the script with a "--debug
On 04/01/11 15:58, Camaleón wrote:
On Mon, 03 Jan 2011 17:54:37 +, Tony van der Hoff wrote:
Can anyone explain why this happens? Should I upgrade phpmyadmin
manually?
Maybe you can run the script with a "--debug" flag ("unattended-upgrades
--debug") to get additional information :-?
Yes
On Mon, 03 Jan 2011 17:54:37 +, Tony van der Hoff wrote:
> I have lenny-based VPS server, which looks after itself pretty well.
> Following the recent security notice regarding PHPMyAdmin, I checked the
> unattended-upgrades log, where I was surprised to notice that it had
> skipped the upgrad
93 matches
Mail list logo
