On Tue, Nov 06, 2018 at 02:30:19PM +0200, juice wrote:
> Lennart Poettering kirjoitti 2018-11-06 12:27:
> > On Di, 06.11.18 11:57, juice ([email protected]) wrote:
> >
> > >
> > > Hi,
> > >
> > > During the past half year I have seen systemd dump core three times
> > > due
> > > to what I suspec
On 11/6/18 9:57 UTC, juice wrote:
During the past half year I have seen systemd dump core three times due
to what I suspect a hashmap corruption or race.
Each time it looks a bit different and is triggered by different things
but it somehow centers on hashmap operations.
Three intermittent har
For repair a hash corruption which a signature for each file are the BASS
framework from Thalos cybersecurity worker that add this program on Clam AV for
check all files signatures ;)
Regards.
Dorian Rosse.
De : systemd-devel de la part de
juice
Envoyé : ma
Lennart Poettering kirjoitti 2018-11-06 12:27:
On Di, 06.11.18 11:57, juice ([email protected]) wrote:
Hi,
During the past half year I have seen systemd dump core three times
due
to what I suspect a hashmap corruption or race.
Each time it looks a bit different and is triggered by different
El 05-11-2018 a las 3:17, piliu escribió:
During this service, the power state can not be got from sysfs, neither
it can be got by systemd's utility. So is it acceptable to signal the
failure of service by a tmp file under /tmp ? I.e adding
FailureAction=touch /tmp/poweroff_fail in systemd-pow
On Di, 06.11.18 11:57, juice ([email protected]) wrote:
>
> Hi,
>
> During the past half year I have seen systemd dump core three times due
> to what I suspect a hashmap corruption or race.
> Each time it looks a bit different and is triggered by different things
> but it somehow centers on hash
Hi,
During the past half year I have seen systemd dump core three times due
to what I suspect a hashmap corruption or race.
Each time it looks a bit different and is triggered by different things
but it somehow centers on hashmap operations.
What would be the prefered way to debug this? I canno
