OK i went to watch that I could go to http://www.ubuntu.com/support,
Sorry finally you can close the ticket,
Regards.
Dorian ROSSE.
De : systemd-devel de la part de
Reindl Harald
Envoyé : Monday, September 17, 2018 4:28:07 PM
À :
I don't know the significance of this error when I start my network
(CentOS 7) but it does not seem to effect anything I've noticed. Can
someone tell me what this means, what it might effect and how to fix it?
TIA.
Sep 16 09:34:38 dap002 systemd[1]: Job
Am 17.09.18 um 15:57 schrieb Tomasz Torcz:
> On Mon, Sep 17, 2018 at 09:27:20AM +, Dorian ROSSE wrote:
>> Hello Dear IT team worker,
>>
>> Since yesterday my running kernel is 4.18.8 instead 4.17.2 but at each
>> reboot I have a system crashed,
>> How to keep this laster running kernel
On Mon, Sep 17, 2018 at 09:27:20AM +, Dorian ROSSE wrote:
> Hello Dear IT team worker,
>
> Since yesterday my running kernel is 4.18.8 instead 4.17.2 but at each reboot
> I have a system crashed,
> How to keep this laster running kernel without have a crash at each reboot ?
Dorian,
this
Hello Dear IT team worker,
Since yesterday my running kernel is 4.18.8 instead 4.17.2 but at each reboot I
have a system crashed,
How to keep this laster running kernel without have a crash at each reboot ?
Thank you in advance to answer my ask,
Regards.
Dorian ROSSE.
Hello,
My embedded board is running systemd v232 and I dont have RTC. So, the logs are
completely depends on wallclock.
I see that the journalctl is doing some optimization in the output and not
printing all the available boots.
root@ubuntu:~# journalctl --list-boots --no-pager
-1
