>>> Andrei Borzenkov schrieb am 11.02.2021 um 15:20 in
Nachricht
:
> On Thu, Feb 11, 2021 at 1:47 PM Ulrich Windl
> wrote:
>>
>> Hi!
>>
>> Suspecting systemd added some requirement that isn't fulfilled after boot,
> preventing my units from starting I wonder:
>> How can I debug systemd's
Hello,
I've been tasked to take a large application mostly written in C which had
previously always run as root and now run it under dynamic user.
My goal is to follow the "principle of least privilege" and figure out all
the necessary individual privileges I need to provide so that it continues
The situation turns out to be a little different, the log messages are
somewhat misleading.
First, my ra intervals were indeed set to high, thanks for the heads up,
after some testing I forgot to set them back. Should have paid more
attention way back. But those where not directly the cause.
On Thu, Feb 11, 2021 at 09:19:07AM -0500, Phillip Susi wrote:
>
> Phillip Susi writes:
>
> > Wait, what do you mean the inode nr changes? I thought the whole point
> > of the block donating thing was that you get a contiguous set of blocks
> > in the new file, then transfer those blocks back to
Colin Guthrie writes:
> I think the defaults are more complex than just "each journal file can
> grow to 128M" no?
Not as far as I can see.
> I mean there is SystemMaxUse= which defaults to 10% of the partition on
> which journal files live (this is for all journal files, not just the
>
Agreed, I run timesyncd on 20+ machines on a bunch of VLANs that are
all IPv6-enabled with RAs being used, and have not seen this symptom.
On Thu, Feb 11, 2021 at 11:23 AM Mantas Mikulėnas wrote:
>
> On Thu, Feb 11, 2021 at 6:07 PM Ede Wolf wrote:
>>
>> Thanks. Indeed, stopping radvd made these
Phillip Susi wrote on 11/02/2021 16:29:
Colin Guthrie writes:
Are those journal files suffixed with a ~. Only ~ suffixed journals
represent a dirty journal file (i.e. from an unexpected shutdown).
Nope.
Journals rotate for other reason too (e.g. user request, overall space
requirements
Colin Guthrie writes:
> Are those journal files suffixed with a ~. Only ~ suffixed journals
> represent a dirty journal file (i.e. from an unexpected shutdown).
Nope.
> Journals rotate for other reason too (e.g. user request, overall space
> requirements etc.) which might explain this
On Thu, Feb 11, 2021 at 6:07 PM Ede Wolf wrote:
> Thanks. Indeed, stopping radvd made these messages stop appearing.
> Now I am no IPv6 guru, but having routeradvertisments is not too
> uncommon, to the best of my knowledge.
>
RAs shouldn't be extremely frequent. An hour is a common interval
Phillip Susi wrote on 11/02/2021 14:19:
Looking at the archived journals though, I wonder why am I seeing so
many unwritten areas? Just the last extent of this file has nearly 4 mb
that were never written to. This system has never had an unexpected
shutdown. Attached is the extent map.
Are
Thanks. Indeed, stopping radvd made these messages stop appearing.
Now I am no IPv6 guru, but having routeradvertisments is not too
uncommon, to the best of my knowledge.
So the punchline is, that timesynd is not really usable with ipv6
networks? Am I getting that correct?
After all, an ra
Phillip Susi writes:
> Wait, what do you mean the inode nr changes? I thought the whole point
> of the block donating thing was that you get a contiguous set of blocks
> in the new file, then transfer those blocks back to the old inode so
> that the inode number and timestamps of the file don't
On Thu, Feb 11, 2021 at 1:47 PM Ulrich Windl
wrote:
>
> Hi!
>
> Suspecting systemd added some requirement that isn't fulfilled after boot,
> preventing my units from starting I wonder:
> How can I debug systemd's requirements checking for units that are enabled,
> but not started at boot
>>> Ulrich Windl schrieb am 11.02.2021 um 11:46 in Nachricht <60250B22.85D :
>>> 161 :
60728>:
> Hi!
>
> Suspecting systemd added some requirement that isn't fulfilled after boot,
> preventing my units from starting I wonder:
> How can I debug systemd's requirements checking for units that are
Hi!
Suspecting systemd added some requirement that isn't fulfilled after boot,
preventing my units from starting I wonder:
How can I debug systemd's requirements checking for units that are enabled, but
not started at boot (status "inactive (dead)"?
Or another way: Can I list the dependencies
On Mi, 10.02.21 16:56, Andreas Krüger (drandreaskrue...@web.de) wrote:
>Hi folks,
>
>I'm freelancer and for my client I'm currently working on a board with
>securtity features running Debian OS and SystemD. Logging is done by
>JournalD and should run in "sealing" mode. For that,
>>> Phillip Susi schrieb am 10.02.2021 um 20:39 in
>>> Nachricht
<878s7v6759@vps.thesusis.net>:
> Chris Murphy writes:
>
>> It's not interleaving. It uses delayed allocation to make random
>> writes into sequential writes. It's tries harder to keep file blocks
>
> Yes, and when you do
>>> Ede Wolf schrieb am 10.02.2021 um 19:39 in
Nachricht
:
> Hi,
>
>
> My journal get spammed with messages from timesyncd, claiming a changed
> network connection. However, I have not touched the network
> configuration at all and the ntp even happens to be on the same subnet.
> No DHCP
18 matches
Mail list logo
