Desktop Software Updates Settings schedule... where are the settings stored?
SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,818
Rep:
Desktop Software Updates Settings schedule... where are the settings stored?
The Leap 15.1 patchs/updates are coming out wa-a-ay more frequently than I figured it would ever be given that it's supposed to be the "stable" release. (Lately, it's been almost as frequent as Tumbleweed's updates. A prelude to 15.2 coming out?)
I had been allowing the Software Update notifier in KDE/Plasma go out and check for new patches daily but I've decided that's too frequent. I've changed it to "Weekly" but I'd like that to be every Fridays. Sadly, there is no qualifier for "Weekly" that lets you specify the day of the week.
Questions:
Q1: Does anyone know where that frequency is saved and whether there are other parameters can be tweaked to have it run on a particular day of the week? I.e., is it a UNIX epoch timestamp that merely gets updated by either 86400 for daily checks, 604800 for weekly, etc.?
Q2: Or... is it possible -- and/or advisable -- to disable the desktop's Software Updates checker altogether and just execute "zypper list-updates -a" in a cron job to provide the same notification but on a schedule that I can set up? I do this on a headless system running Tumbleweed and it works well to let me know when it's time to run "zypper dup".
I don't think I've ever run a desktop software updater on any distro. On Leap, as with prior releases dating back to the inception of Zypper somewhere around 11.0, I've been updating on a purely ad hoc basis, but on average run zypper up sometime over around every other weekend, most often on a Saturday. Last was 167 packages about 24 hours ago, and prior 17 days ago. Some of those 167, mostly libreoffice*, I hadn't been allowing to update via zypper locks for quite some time, to save bandwidth attributable to large software rarely used.
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,818
Original Poster
Rep:
Quote:
Originally Posted by mrmazda
I've been updating on a purely ad hoc basis, but on average run zypper up sometime over around every other weekend, most often on a Saturday.
So I'll be looking at running a cron job running "zypper list-updates -a" and issuing "zypper up" when the cron job indicates there are updates to deal with.
Quote:
Some of those 167, mostly libreoffice*, I hadn't been allowing to update via zypper locks for quite some time, to save bandwidth attributable to large software rarely used.
I had an ugly LO update last summer that had me downgrading it and locking it. Operated that way for several months before I decided to give a newer version a try. I'm not all that concerned about the bandwidth for updates. What I found annoying when I was running Tumbleweed on my laptop was the frequency with which everything TeX- and LaTeX-related was getting updated---there must have been 1700+ individual packages that needed to be downloaded and installed (roughly once a month it seemed) and those took forever. Whatever I'd planned on getting done on the laptop that evening was blown out of the water when those were part of the updates. Like the CM fonts actually required an update. It was the impetus for moving that system to Slackware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.