Hi!
As a routine update, only one package was updated: snapd.
Why "needrestart" told me to restart all these services?!
On Fri, 6 May 2022 19:29:35 +0100, Paulo da Silva wrote:
Hi!
As a routine update, only one package was updated: snapd.
Why "needrestart" told me to restart all these services?!
Note I run Mageia Linux and have no experience with "needrestart"
I do know when sysetmd detects a new service file it ask for you to
reload it or all services. Sounds like the message may have triggered "needrestart" to suggest you to do whatever it asked.
Às 20:00 de 06/05/22, Bit Twister escreveu:
On Fri, 6 May 2022 19:29:35 +0100, Paulo da Silva wrote:
Hi!
As a routine update, only one package was updated: snapd.
Why "needrestart" told me to restart all these services?!
Note I run Mageia Linux and have no experience with "needrestart"
I do know when sysetmd detects a new service file it ask for you toAnyway, why does a single package like snapd, which I could easily
reload it or all services. Sounds like the message may have
triggered "needrestart" to suggest you to do whatever it asked.
remove, trigger so much services seeming not related at all?
I do know when sysetmd detects a new service file it ask for you to
reload it or all services. Sounds like the message may have triggered "needrestart" to suggest you to do whatever it asked.
On 5/6/22 12:00, Bit Twister wrote:
I do know when sysetmd detects a new service file it ask for you to
reload it or all services. Sounds like the message may have triggered
"needrestart" to suggest you to do whatever it asked.
If systemd detects an existing unit file change, or a new service unit
file is created, it should only ever ask for a simple 'systemctl daemon-reload'.
On Fri, 6 May 2022 19:29:35 +0100, Paulo da Silva wrote:
Hi!
As a routine update, only one package was updated: snapd.
Why "needrestart" told me to restart all these services?!
Note I run Mageia Linux and have no experience with "needrestart"
I do know when sysetmd detects a new service file it ask for you to
reload it or all services. Sounds like the message may have triggered "needrestart" to suggest you to do whatever it asked.
Hi!
As a routine update, only one package was updated: snapd.
Why "needrestart" told me to restart all these services?!
systemctl restart colord.service NetworkManager.service nmbd.service smbd.service ssh.service systemd-journald.service systemd-logind.service systemd-resolved.service systemd-timesyncd.service systemd-udevd.service udisks2.service whoopsie.service wpa_supplicant.service
Thanks for any comments.
On Fri, 6 May 2022 22:53:58 -0700, stepore wrote:
On 5/6/22 12:00, Bit Twister wrote:
I do know when sysetmd detects a new service file it ask for you to
reload it or all services. Sounds like the message may have triggered
"needrestart" to suggest you to do whatever it asked.
If systemd detects an existing unit file change, or a new service unit
file is created, it should only ever ask for a simple 'systemctl
daemon-reload'.
I agree, that is all I have ever seen on my install. Sounds like the
wraooer script has decided to always have user restart services to pick
up any possible service app changes.
Any time I want to run down systemdd problems like dependence or booting problems I do a
systemd-analyze plot > /var/tmp/blame.svg
firefox /var/tmp/blame.svg &
other tools
systemd-analyze blame
systemd-analyze critical-chain
Hi!
As a routine update, only one package was updated: snapd.
Why "needrestart" told me to restart all these services?!
systemctl restart colord.service NetworkManager.service nmbd.service smbd.service ssh.service systemd-journald.service systemd-logind.service systemd-resolved.service systemd-timesyncd.service systemd-udevd.service udisks2.service whoopsie.service wpa_supplicant.service
Thanks for any comments.
<snip> I only have blender,
shotcut and pycharm-community as snap packages!
On 5/6/22 11:29, Paulo da Silva wrote:
Hi!
As a routine update, only one package was updated: snapd.
Why "needrestart" told me to restart all these services?!
systemctl restart colord.service NetworkManager.service nmbd.service
smbd.service ssh.service systemd-journald.service systemd-logind.service
systemd-resolved.service systemd-timesyncd.service systemd-udevd.service
udisks2.service whoopsie.service wpa_supplicant.service
Thanks for any comments.
snapd has it's hooks in all these system services because they effect
the packages inside the snap 'containers'.
On a side note, if you're not using some of these you should disable
them. like smbd/nmbd (if you're not using windows files sharing, etc) systemctl disable serviceunitname.service
On 5/7/22 18:35, Paulo da Silva wrote:
<snip> I only have blender,
shotcut and pycharm-community as snap packages!
That doesn't sound right. You sure? If you're using snap you should have
some default base core, gtk and gnome packages installed as snaps too.
Unless you've deleted them. But that would probably break snapd.
what does 'snap list' show?
blender 3.1.2 2106 latest/stable blenderfoundation✓ classic
core 16-2.54.4 12834 latest/stable canonical✓ core
core18 20220309 2344 latest/stable canonical✓ base
pycharm-community 2022.1 276 latest/stable jetbrains✓
classic
shotcut 22.04.25 692 latest/stable meltytech✓
classic
snapd 2.55.3 15534 latest/stable canonical✓
snapd
I am using kubuntu 20.04, not ubuntu.
On 5/8/22 10:16, Paulo da Silva wrote:
blender 3.1.2 2106 latest/stable blenderfoundation✓
classic
core 16-2.54.4 12834 latest/stable
canonical✓ core
core18 20220309 2344 latest/stable
canonical✓ base
pycharm-community 2022.1 276 latest/stable jetbrains✓
classic
shotcut 22.04.25 692 latest/stable meltytech✓
classic
snapd 2.55.3 15534 latest/stable canonical✓
snapd
I am using kubuntu 20.04, not ubuntu.
Desktop environment doesn't matter. if you're using snapd then it'll
still have its hooks into all those services.
For instance. snapd.socket unit file contains:
WantedBy=sockets.target
And sockets.target has all these type of unit files listed: /etc/systemd/system/sockets.target.wants/acpid.socket
/etc/systemd/system/sockets.target.wants/apport-forward.socket
/etc/systemd/system/sockets.target.wants/avahi-daemon.socket
/etc/systemd/system/sockets.target.wants/cups.socket
/etc/systemd/system/sockets.target.wants/snapd.socket
/etc/systemd/system/sockets.target.wants/uuidd.socket
/etc/systemd/user/sockets.target.wants/dirmngr.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-browser.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-extra.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-ssh.socket
/etc/systemd/user/sockets.target.wants/gpg-agent.socket
/etc/systemd/user/sockets.target.wants/pk-debconf-helper.socket
/etc/systemd/user/sockets.target.wants/pulseaudio.socket
/snap/core18/2344/lib/systemd/system/sockets.target
/snap/core18/2344/lib/systemd/system/sockets.target.wants
/snap/core18/2344/lib/systemd/system/sockets.target.wants/dbus.socket
/snap/core18/2344/lib/systemd/system/sockets.target.wants/systemd-initctl.socket
/snap/core18/2344/lib/systemd/system/sockets.target.wants/systemd-journald-audit.socket
/snap/core18/2344/lib/systemd/system/sockets.target.wants/systemd-journald-dev-log.socket
/snap/core18/2344/lib/systemd/system/sockets.target.wants/systemd-journald.socket
/snap/core18/2344/lib/systemd/system/sockets.target.wants/systemd-udevd-control.socket
/snap/core18/2344/lib/systemd/system/sockets.target.wants/systemd-udevd-kernel.socket
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 499 |
Nodes: | 16 (2 / 14) |
Uptime: | 29:38:54 |
Calls: | 9,832 |
Calls today: | 2 |
Files: | 13,761 |
Messages: | 6,192,496 |