resolv.conf questions

[Ralf Mardorf]

On Wed,  7 Aug 2019 14:26:52 -0400 (EDT), Robert Heller wrote:
>OR just restart systemd-resolved (no real need to reboot -- that is a
>silly mess-windows habit):

So you expect all users to become experts? If you e.g. close evolution,
then upgrade evolution, you cannot just restart evolution after
the upgrade, you need to kill all evolution processes after the upgrade.

When closing not all evolution processes are terminated, if you
manually kill all evolution processes and you are running some
gnome-shell thingy, it will restart one or the other evolution process.
So even killing the processes by command line needs to be done after
the upgrade. You need to be aware about such things.

Should I continue with examples?

How about https://packages.ubuntu.com/disco/all/rtirq-init/filelist ?

In Ubuntu its does still use an init script, while upstream and other
distros already use a systemd unit.

However, if you reconfigure rtirq and you restart it (either via an
init script or systemd), it should do the job, but actually it not
necessarily does, a reboot could be required.

How about Linux memory issues? I'm a power user and don't know the
steps to handle those by command line and even those who have got the
skills seem to be in favour of rebooting the machine, perhaps just for
time reasons.

You expect a user to know when restarting a service does the job and
when a reboot could be needed. You expect a user to know how to handle
each application, IOW to know that some apps might run several
processes and another process unrelated to the app might restart those
processes?

It's ridiculous, just a few power users have this knowledge and even
those easily could miss something.

A reboot is not "a silly mess-windows habit", it's the only sane way to
not accidentally miss something for experts with much knowledge and the
only way at all for Jane Dow even when using Linux. Actually even
Windows not necessarily requires a restart, it's just the safest way to
ensure that everything is in place.

Reboots are silly, if Microsoft or Apple support mentions them as the
only shot in the dark troubleshooting step, but apart from this
restarting a machine in general isn't a bad idea.