On Fr, 23.04.21 14:15, Pengpeng Sun ([email protected]) wrote:
> Hi Lennart,
>
> The issue reproduced at 2021-04-22T15:45:30.230Z, I ran 'sudo journalctl
> -b', the log began at Apr 22 15:45:48 which is later than the issue
> reproduced.
> How can I get more early and detailed systemd log?
On Fr, 23.04.21 11:24, Stephen Hemminger ([email protected]) wrote:
> On Fri, 6 Sep 2019 16:04:33 +0100
> Simon McVittie wrote:
>
> > On Fri, 06 Sep 2019 at 06:57:22 +, Ray, Ian (GE Healthcare) wrote:
> > > If thread-safety is a design goal (and I don’t believe that it is [1])
> > >
On Fri, 6 Sep 2019 16:04:33 +0100
Simon McVittie wrote:
> On Fri, 06 Sep 2019 at 06:57:22 +, Ray, Ian (GE Healthcare) wrote:
> > If thread-safety is a design goal (and I don’t believe that it is [1])
> > then atomic or thread-safe primitives should be used.
> >
> > [1]
> > https://lists.fre
On Thu, 2021-04-22 at 21:40 -0400, Martin K. Petersen wrote:
>
> Martin,
>
> > I suppose 99.9% of users never bother with customizing the udev
> > rules.
>
> Except for the other 99.9%, perhaps? :) We definitely have many users
> that tweak udev storage rules for a variety of reasons. Including
On 4/22/21 11:00 AM, Mantas Mikulėnas wrote:
> ...
> I'm curious about what brought this problem into existence in the
> first place. Why *is* it necessary to contact a random address within
> the network? (If it's to check that the physical interface is working,
> then just the fact that you someh
Hi Lennart,
The issue reproduced at 2021-04-22T15:45:30.230Z, I ran 'sudo journalctl -b',
the log began at Apr 22 15:45:48 which is later than the issue reproduced.
How can I get more early and detailed systemd log?
--
Best regards,
Pengpeng
On 2021/4/23, 4:01 PM, "Lennart Poettering" wrote
On Fri, Apr 23, 2021 at 10:00:32 +0200 Lennart Poettering
wrote:
> On Fr, 23.04.21 08:17, Paul Menzel ([email protected])
> wrote:
>
> > Dear systemd folks,
> >
> >
> > Due to historical reasons, in our environment we have a configuration file
> > with the network device name an
On Di, 20.04.21 16:48, Pengpeng Sun ([email protected]) wrote:
> Thanks Lennart!
> I reproduced the issue after set "systemd-analyze log-level debug". It turns
> out 'systemctl reboot' triggered before all the steps logged in 'journalctl
> -a'. But I did get the stderr of 'systemctl reboot',
On Fr, 23.04.21 08:17, Paul Menzel ([email protected]) wrote:
> Dear systemd folks,
>
>
> Due to historical reasons, in our environment we have a configuration file
> with the network device name and the to be assigned IP address:
>
> $ more /etc/local/mxhost.conf
> MX_NE
>>> "Bruce A. Johnson" schrieb am 22.04.2021
um
22:14 in Nachricht
<[email protected]>:
> I'm still trying to get an explanation of why having a valid DHCP
> address is not in itself good enough. The only reason I've been able to
> see is that after the l
10 matches
Mail list logo
