On Thu, 14 May 2020 at 16:12:49 +0300, Mantas Mikulėnas wrote:
> The "--Reboot--" line is simply shown every time the _BOOT_ID field changes
> between two entries -- even if it changes to a previously seen boot ID (which
> shouldn't happen normally, but *might* be caused by lack of a RTC?).
The Ra
On Do, 14.05.20 16:11, Dave Howorth (syst...@howorth.org.uk) wrote:
>
> I've never even heard of a _BOOT_ID before, so it seems I'll need to do
> some reading to answer my original questions. Where's a good place to
> start?
The _BOOT_ID is simply random ID associated with every boot by the
kerne
On Thu, 14 May 2020 16:12:49 +0300
Mantas Mikulėnas wrote:
> On Thu, May 14, 2020 at 3:55 PM Dave Howorth
> wrote:
>
> > What do --Reboot-- lines in the journal mean and how do they get
> > there?
> >
> > I can't find any explanation on
> > https://www.freedesktop.org/software/systemd/man/journa
On Thu, May 14, 2020 at 3:55 PM Dave Howorth wrote:
> What do --Reboot-- lines in the journal mean and how do they get there?
>
> I can't find any explanation on
> https://www.freedesktop.org/software/systemd/man/journalctl.html or
> related pages I've tried.
>
> I should explain why I'm interest
> What do --Reboot-- lines in the journal mean and how do they get there?
IIRC these mean that system was restarted.
--
Łukasz Niemier
luk...@niemier.pl
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/m
What do --Reboot-- lines in the journal mean and how do they get there?
I can't find any explanation on
https://www.freedesktop.org/software/systemd/man/journalctl.html or
related pages I've tried.
I should explain why I'm interested. On my openSUSE box, I can see for
example:
# journalctl --lis
On Do, 07.05.20 10:00, de...@gmx.de (de...@gmx.de) wrote:
> Hi there!
>
> I'm on a Yocto system with latest v241 stable systemd. The odd thing
Latest stable systemd release is actually v245.
Consider updating, there's a good chance this already works on less
old systemd.
> is, that systemd-netw
Am 06.05.20 um 11:49 schrieb Ulrich Windl:
Reindl Harald schrieb am 06.05.2020 um 11:24 in
> Nachricht
> <11141_1588757087_5EB2825F_11141_72_1_3a082624-966b-a922-f8b9-ef0bb69c32f0@thelo
> nge.net>:
>
>>
>> Am 06.05.20 um 11:21 schrieb Ulrich Windl:
>>> # systemctl kill -s HUP --kill-who=15
Am 06.05.20 um 11:21 schrieb Ulrich Windl:
> # systemctl kill -s HUP --kill-who=15862 iotwatch@LOC1.service
>
> Did I misinterpret the manual page, or what is the problem?
>
>--kill-who=
>When used with kill, choose which processes to send a signal to.
>Must be
Am 30.04.20 um 13:20 schrieb Mark Bannister:
>> On Mon, 2020-04-27 at 11:40 +0100, Mark Bannister wrote:
>
>>> One of the error messages I've been trying to explain is reported like this:
>>> 2020-04-22T00:45:47.047710-04:00 jupiter systemd[1]: Requested transaction
>>> contradicts existing job
Am 22.04.20 um 16:44 schrieb Peter Morrow:
> I'm trying to optimise our boot process and have started to look at
> the time it takes for the network to come up (a single interface to be
> routable) when using systemd-networkd:
>
> So, here systemd-networkd-wait-online.service seems to run for 3.
the cpu time of 672ms is wrong, memory is missing in Fedora 31 while it
was there in previous versions though it's a oneshot service
*after* stop the service the correct cpu usage of it's lifetime is logged
[root@srv-rhsoft:~]$ systemctl status guest-arrakis.service
● guest-arrakis.service - VMw
12 matches
Mail list logo
