On Sun, Oct 9, 2016 at 7:33 AM, Nico Kadel-Garcia <nkadel(a)gmail.com> wrote:
I must suggest that "nohup dnf whatever > logfile.out
&" is your
friend for exactly this sort of thing. stdin/stdout/stderr are all
disconnected from the running session and a visible log is generated.
Thanks very much for taking the time to post... very simple and to the
point.
Another method I've found for those concerned about using a terminal under
a DE is to
check out dnf-automatic:
https://fedoraproject.org/wiki/AutoUpdates
There is currently an open bug regarding the use of email notifications
when using
dnf-automatic:
https://bugzilla.redhat.com/show_bug.cgi?id=1279773
but other than that, it appears to work fine.
For those wanting to know which processes need to be restarted after
update,
there is the appropriately named dnf needs-restarting:
http://dnf-plugins-core.readthedocs.io/en/latest/needs_restarting.html
As the documentation mentions:
Note that in most cases a process should survive update of its binary and
libraries
it is using without requiring to be restarted for proper operation.
There are however specific cases when this does not apply.