I agree that i should have had much lower log level.
This is now fixed properly upstream via
https://github.com/systemd/systemd/pull/18638/files
I will try to backport that to stable series or at least drop the log
level to debug.
On Mon, 19 Oct 2020 at 15:05, Michael Biebl wrote:
>
> Am Mo.,
Right, in systemd's case there's no access to the external namespaces, but
being the first process in a container allows you to take a snapshot of
/proc/1/mountinfo during initialization (the container runtime would have
all the initial mountpoints ready by then), and store all these mountpoints
an
On Sa, 27.02.21 11:28, Rodny Molina ([email protected]) wrote:
> Thanks for your detailed answer / explanation Lennart, it's fully
> consistent with my code-browsing findings.
>
> I've been struggling myself with the problem that you alluded above to
> identify "foreign" mountpoints. After ban
Thanks for the insight.
W dniu 01.03.2021 o 17:34, Lennart Poettering pisze:
> On Mo, 01.03.21 17:17, Michał Zegan ([email protected]) wrote:
>
>>> But this stuff is racy of course if the RTC is compiled as module and
>>> you care for generic hw, that might or might not have an RTC: we
>
On Mo, 01.03.21 17:17, Michał Zegan ([email protected]) wrote:
> > But this stuff is racy of course if the RTC is compiled as module and
> > you care for generic hw, that might or might not have an RTC: we
> > cannot gues swhether an RTC will show up or not in that case,
> > i.e. whether
W dniu 01.03.2021 o 17:19, Lennart Poettering pisze:
> On Mo, 01.03.21 17:09, Michał Zegan ([email protected]) wrote:
>
There are problems with log timestamps when you do that, and it is
probably why it was not done.
I am wondering if the only correct way isn't to do it i
On Mo, 01.03.21 17:09, Michał Zegan ([email protected]) wrote:
> >> There are problems with log timestamps when you do that, and it is
> >> probably why it was not done.
> >> I am wondering if the only correct way isn't to do it in initramfs (if
> >> it's systemd) before starting the jour
W dniu 01.03.2021 o 16:59, Lennart Poettering pisze:
> On Mo, 01.03.21 14:52, Michał Zegan ([email protected]) wrote:
>
>> Someone should really find a way to make it cooperate well with modular
>> rtcs.
>> It's popping up over and over and over and over again and no one is/will
>> buil
On Mo, 01.03.21 10:20, John Ioannidis ([email protected]) wrote:
> How can I trace what sd_notify(3) calls a program makes?
strace. sd_notify() is just a wrapper around the sendmsg() syscall,
and you'll see that in strace.
> Obviously, I don't have the source, and running *strings* on it doe
W dniu 01.03.2021 o 17:01, Lennart Poettering pisze:
> On Mo, 01.03.21 15:38, Michał Zegan ([email protected]) wrote:
>
>> There are problems with log timestamps when you do that, and it is
>> probably why it was not done.
>> I am wondering if the only correct way isn't to do it in init
On Mo, 01.03.21 15:38, Michał Zegan ([email protected]) wrote:
> There are problems with log timestamps when you do that, and it is
> probably why it was not done.
> I am wondering if the only correct way isn't to do it in initramfs (if
> it's systemd) before starting the journald, so tha
On Mo, 01.03.21 14:52, Michał Zegan ([email protected]) wrote:
> Someone should really find a way to make it cooperate well with modular
> rtcs.
> It's popping up over and over and over and over again and no one is/will
> build all rtc drivers into the kernel.
To my knowledge the kernel
How can I trace what sd_notify(3) calls a program makes?
Obviously, I don't have the source, and running *strings* on it does reveal
a *READY=1* line, but it is unclear whether the code makes it to the point
where that gets sent.
Here is what I am *really* trying to accomplish; maybe I am going a
There are problems with log timestamps when you do that, and it is
probably why it was not done.
I am wondering if the only correct way isn't to do it in initramfs (if
it's systemd) before starting the journald, so that first saved logs
have correct timestamps?
W dniu 01.03.2021 o 15:28, Kevin P.
It's fairly simple to add a one-shot service unit to use 'hwclock' to
read from the RTC and set the kernel's real-time clock. I do this on
my RPis which use modules for their RTCs.
On Mon, Mar 1, 2021 at 9:02 AM Michał Zegan wrote:
>
> Someone should really find a way to make it cooperate well wi
Someone should really find a way to make it cooperate well with modular
rtcs.
It's popping up over and over and over and over again and no one is/will
build all rtc drivers into the kernel.
W dniu 01.03.2021 o 13:04, Mantas Mikulėnas pisze:
> Normally I think systemd expects the kernel to do this
Normally I think systemd expects the kernel to do this on its own.
On Mon, Mar 1, 2021, 12:31 Belisko Marek wrote:
> Hi,
>
> I have a case when a board boots without network connection but RTC
> have the correct date/time. Does systemd use RTC date/time to set
> systemd time or it needs to be do
Hi,
I have a case when a board boots without network connection but RTC
have the correct date/time. Does systemd use RTC date/time to set
systemd time or it needs to be done manually?
Thanks and regards,
marek
--
as simple and primitive as possible
-
18 matches
Mail list logo
