On Sun, 25 Mar 2018 09:27:01 +0200
François Patte <francois.patte(a)mi.parisdescartes.fr> wrote:
On my f27 there is a netconsole service but, it starts before the
network service and so fails to be launched... As it is a sysv service,
I don't know how to confgure this service to start after network.
An option then might be to start the network on boot-up as soon
as possible, and on shutdown to take it down as late as possible.
As to the latter see one of the messages of Eyal Lebedinsky in
"In my experience the network is taken down before the end of the
messages so you miss some."
Thanks, Eyal, for pointing to this ..
So on shutdown netconsole might be disconnected a little bit too
early, IIUC ...
That is, the order of starting services seems important.
In old sysv, IIRC, it was easy, to order the startup or shutdown
of services with something like creating simple K[NN] or S[NN] links
to maybe /etc/init.d/, -- not so now with systemd ..
A not so helpful starting point might be "man systemd.preset".
Also: the files in /etc/systemd/system/ might give clues.
The trick seems to be for startup to create a netconsole.service
(you might see its status via 'systemctl status netconsole'), and to
start networking before netconsole.
Maybe it's neccessary to create it for
/etc/systemd/system/ via 'systemd-sysv-install enable netconsole'
but that's a guess - don't do it until you're sure about it.
/usr/lib/systemd/systemd-sysv-install is-enabled netconsole
Yes, that looks strange: it seems systemctl doesn't support natively
netconsole, diverting action to 'systemd-sysv-install'
Look at this:
% systemctl is-enabled netconsole
netconsole.service is not a native service, redirecting to systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install is-enabled netconsole
Some hints on how to organize the timing of startup services:
(see 'Unit order' on that page .. )
I have to set up netconsole for myself - so I might be back if I know