So the bug is invalid right?
** Changed in: update-notifier (Ubuntu)
Importance: Undecided => Low
** Changed in: update-notifier (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Hello,
I have found a reason.
I use check_mk_agent with mk_apt plugin: https://mathias-
kettner.de/cms_check_apt.html
I ignored recommendation of the check-mk developers and installed the plugin
without any interval:
It is recommended to install this plugin with asynchronous execution and at an
** Changed in: update-notifier (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828634
Title:
update-notifier runs too often on a Ubuntu
To manage notificati
Hello Steve, all,
Thank for your activity. But something looks strange...
I am using standard update-notifier utility from official Ubuntu repo.
My PC is running 1h:
vodka@vodka-PC:/proc/9489$ uptime
12:56:19 up 1:00, 1 user, load average: 0,40, 0,56, 0,60
I determined the process PID for up
I'm sorry, I don't know what app you used to determine that update-
notifier was writing to disk, but I don't think this analysis is
correct. update-notifier certainly *shouldn't* be writing to disk, and
an strace of update-notifier on my desktop (Ubuntu 19.04, same as this
report) over a 10minute
