Re: Restarting systemd
On Mon, 2017-03-06 at 06:17 -0500, Tom H wrote:
On Sun, Mar 5, 2017 at 4:04 PM, Patrick O'Callaghan
<pocallaghan(a)gmail.com> wrote:
> On Sun, 2017-03-05 at 14:17 -0500, Tom H wrote:
> > On Sun, Mar 5, 2017 at 9:44 AM, Patrick O'Callaghan
> > <pocallaghan(a)gmail.com> wrote:
> > > On Sun, 2017-03-05 at 08:32 -0500, Tom H wrote:
> > > > On Sun, Mar 5, 2017 at 6:15 AM, Patrick O'Callaghan
> > > > <pocallaghan(a)gmail.com> wrote:
> > > > >
> > > > > 'dnf update' (using the tracer plugin) often tells me to
restart
> > > > > certain services via systemctl, which is fine. However on
occasion it
> > > > > tells me to restart something manually. I can usually figure out
how
> > > > > to do this, but the one I can't figure out is systemd
itself:
> > > > >
> > > > > ...
> > > > > You should restart:
> > > > > * These applications manually:
> > > > > systemd
> > > > > # systemctl daemon-reexec
> > > > > # tracer
> > > > > You should restart:
> > > > > * These applications manually:
> > > > > systemd
> > > > >
> > > > > Sending HUP, TERM etc. to systemd doesn't make any
difference.
> > > > >
> > > > > Is there a way to do this without rebooting?
> > > >
> > > > systemctl daemon-reload
> > > > or
> > > > systemctl daemon-reexec
> > >
> > > As I said above, that doesn't work.
> >
> > I'm sorry. I (somehow!) didn't see your "systemctl
daemon-reexec".
> > Amazing and embarrassing.
>
> Errare uHmanum est.
Indeed :(
I've just run "systemctl daemon-reexec" in a VM and "journalctl"
shows
"Reexecuting".
I checked "/proc/1/map_files/" and everything'd definitely been remapped.
You should probably file a bug against "tracer".
OK, I'll check that.
poc