On 2022-03-02 15:54, Larry Len Rainey wrote:
I tried to send this to opensuse support but I got rejected - probably the wrong place again - so excuse me.
Use plain text mail.
-------- Forwarded Message -------- Subject: Date: From: To: opensuse support support@lists.opensuse.org
From journalctl - I see packagekit running every 10 minutes. When I attempt a zypper up or zypper dup (tumbleweed), I get
Code:
Ask PackageKit to quit? [yes/no] (no): no System management is locked by the application with pid 17101 (/usr/lib/packagekitd). Close this application before trying again.
which is annoying. How can I get packagekit to only run once an hour instead of 6 times an hour. I know it has to be started with packagekitd but no man page for packagekitd
Telcontar:~ # rpm -qfl /usr/lib/packagekitd | grep usr/share/man /usr/share/man/man1/pkcon.1.gz /usr/share/man/man1/pkmon.1.gz Telcontar:~ #
Code:
VM1:/etc/systemd # man packagekitd No manual entry for packagekitd VM1:/etc/systemd # man packagekit No manual entry for packagekit VM1:/etc/systemd #
Anyone know where - I see this as excessive bandwidth and rather wasteful as few if any of us look to see if an update is ready that often.
This would reduce overhead on the repositories if they were queried fewer times an hour.
Telcontar:~ # rpm -qfl /usr/lib/packagekitd | grep systemd /usr/lib/systemd/system/packagekit-background.service /usr/lib/systemd/system/packagekit-background.timer /usr/lib/systemd/system/packagekit.service Telcontar:~ #
Telcontar:~ # systemctl cat packagekit-background.timer # /usr/lib/systemd/system/packagekit-background.timer [Unit] Description=Systemd timer to update the system daily with PackageKit
[Timer] OnCalendar=daily AccuracySec=12h Persistent=true Unit=packagekit-background.service
[Install] WantedBy=timers.target Telcontar:~ #
That's on Leap.
On 02.03.2022 18:05, Carlos E. R. wrote:
On 2022-03-02 15:54, Larry Len Rainey wrote:
I tried to send this to opensuse support but I got rejected - probably the wrong place again - so excuse me.
Use plain text mail.
-------- Forwarded Message -------- Subject: Date: From: To: opensuse support support@lists.opensuse.org
From journalctl - I see packagekit running every 10 minutes. When I attempt a zypper up or zypper dup (tumbleweed), I get
Code:
Ask PackageKit to quit? [yes/no] (no): no System management is locked by the application with pid 17101 (/usr/lib/packagekitd). Close this application before trying again.
which is annoying. How can I get packagekit to only run once an hour instead of 6 times an hour.
Packagekit is server that is activated on client request. Clients are usually desktop applications. Find out what application triggers packagekit.
I know it has to be started with packagekitd but no man page for packagekitd
Telcontar:~ # rpm -qfl /usr/lib/packagekitd | grep usr/share/man /usr/share/man/man1/pkcon.1.gz /usr/share/man/man1/pkmon.1.gz Telcontar:~ #
Code:
VM1:/etc/systemd # man packagekitd No manual entry for packagekitd VM1:/etc/systemd # man packagekit No manual entry for packagekit VM1:/etc/systemd #
Anyone know where - I see this as excessive bandwidth and rather wasteful as few if any of us look to see if an update is ready that often.
This would reduce overhead on the repositories if they were queried fewer times an hour.
Telcontar:~ # rpm -qfl /usr/lib/packagekitd | grep systemd /usr/lib/systemd/system/packagekit-background.service /usr/lib/systemd/system/packagekit-background.timer
That is one possibility, but even those units are normally disabled by default.
/usr/lib/systemd/system/packagekit.service Telcontar:~ #
Telcontar:~ # systemctl cat packagekit-background.timer # /usr/lib/systemd/system/packagekit-background.timer [Unit] Description=Systemd timer to update the system daily with PackageKit
[Timer] OnCalendar=daily AccuracySec=12h Persistent=true Unit=packagekit-background.service
[Install] WantedBy=timers.target Telcontar:~ #
That's on Leap.
On 2022-03-02 09:05:50 Carlos E. R. wrote:
|On 2022-03-02 15:54, Larry Len Rainey wrote: |> I tried to send this to opensuse support but I got rejected - probably |> the wrong place again - so excuse me. | |Use plain text mail. | |> -------- Forwarded Message -------- |> Subject: |> Date: |> From: |> To: opensuse support support@lists.opensuse.org |> |> |> |> From journalctl - I see packagekit running every 10 minutes. |> When I attempt a zypper up or zypper dup (tumbleweed), I get |> |> Code: |> |> Ask PackageKit to quit? [yes/no] (no): no |> System management is locked by the application with pid 17101 |> (/usr/lib/packagekitd). Close this application before trying again. |> |> which is annoying. |> How can I get packagekit to only run once an hour instead of 6 times an |> hour. |> I know it has to be started with packagekitd but no man page for |> packagekitd | |Telcontar:~ # rpm -qfl /usr/lib/packagekitd | grep usr/share/man |/usr/share/man/man1/pkcon.1.gz |/usr/share/man/man1/pkmon.1.gz |Telcontar:~ # | |> Code: |> |> VM1:/etc/systemd # man packagekitd |> No manual entry for packagekitd |> VM1:/etc/systemd # man packagekit |> No manual entry for packagekit |> VM1:/etc/systemd # |> |> Anyone know where - I see this as excessive bandwidth and rather |> wasteful as few if any of us look to see if an update is ready that |> often. |> |> This would reduce overhead on the repositories if they were queried |> fewer times an hour. | |Telcontar:~ # rpm -qfl /usr/lib/packagekitd | grep systemd |/usr/lib/systemd/system/packagekit-background.service |/usr/lib/systemd/system/packagekit-background.timer |/usr/lib/systemd/system/packagekit.service |Telcontar:~ # | | |Telcontar:~ # systemctl cat packagekit-background.timer |# /usr/lib/systemd/system/packagekit-background.timer |[Unit] |Description=Systemd timer to update the system daily with PackageKit | |[Timer] |OnCalendar=daily |AccuracySec=12h |Persistent=true |Unit=packagekit-background.service | |[Install] |WantedBy=timers.target |Telcontar:~ # | | |That's on Leap.
From what I read on the PackageKit website, it's mostly only useful for folks like Felix who administer multiple distros. I question why it seems to be installed by default. I removed it from my machine back in Leap 15.2.
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.3 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.11 tde-config: 1.0
On 2022-03-03 06:17, J Leslie Turriff wrote:
On 2022-03-02 09:05:50 Carlos E. R. wrote:
|On 2022-03-02 15:54, Larry Len Rainey wrote:
...
From what I read on the PackageKit website, it's mostly only useful for folks like Felix who administer multiple distros. I question why it seems to be installed by default. I removed it from my machine back in Leap 15.2.
Because it can be used by plain user, not admin. It permits things like a media player being started, finding a codec missing, and trigering its install automatically. Or a printer driver. That besides doing normal updates by plain user.
On 2022-03-03 03:28:22 Carlos E. R. wrote:
|On 2022-03-03 06:17, J Leslie Turriff wrote: |> On 2022-03-02 09:05:50 Carlos E. R. wrote: |>> |On 2022-03-02 15:54, Larry Len Rainey wrote: | |... | |> From what I read on the PackageKit website, it's mostly only useful for |> folks like Felix who administer multiple distros. I question why it |> seems to be installed by default. I removed it from my machine back in |> Leap 15.2. | |Because it can be used by plain user, not admin. It permits things like |a media player being started, finding a codec missing, and trigering its |install automatically. Or a printer driver. That besides doing normal |updates by plain user.
Okay.
Leslie --
On 2022-03-03 21:53, J Leslie Turriff wrote:
On 2022-03-03 03:28:22 Carlos E. R. wrote:
|On 2022-03-03 06:17, J Leslie Turriff wrote: |> On 2022-03-02 09:05:50 Carlos E. R. wrote: |>> |On 2022-03-02 15:54, Larry Len Rainey wrote: | |... | |> From what I read on the PackageKit website, it's mostly only useful for |> folks like Felix who administer multiple distros. I question why it |> seems to be installed by default. I removed it from my machine back in |> Leap 15.2. | |Because it can be used by plain user, not admin. It permits things like |a media player being started, finding a codec missing, and trigering its |install automatically. Or a printer driver. That besides doing normal |updates by plain user.
Okay.
Notice that I also uninstall it as a matter of routine ;-)
-
Andrei Borzenkov -
Carlos E. R. -
J Leslie Turriff