On Sat, Oct 2, 2021, at 14:52, Sebastian Benoit wrote:
> abyx...@mnetic.ch(abyx...@mnetic.ch) on 2021.10.01 09:56:32 -0400:
>> On Fri, Oct 1, 2021, at 09:44, Stuart Henderson wrote:
>> > On 2021/10/01 14:43, Stuart Henderson wrote:
>> >> On 2021/10/01 09:29, abyx...@mnetic.ch wrote:
>> >> > I'm get
abyx...@mnetic.ch(abyx...@mnetic.ch) on 2021.10.01 09:56:32 -0400:
> On Fri, Oct 1, 2021, at 09:44, Stuart Henderson wrote:
> > On 2021/10/01 14:43, Stuart Henderson wrote:
> >> On 2021/10/01 09:29, abyx...@mnetic.ch wrote:
> >> > I'm getting a daily crash (call to fatalx). No clue what triggers it
On Fri, Oct 1, 2021, at 09:44, Stuart Henderson wrote:
> On 2021/10/01 14:43, Stuart Henderson wrote:
>> On 2021/10/01 09:29, abyx...@mnetic.ch wrote:
>> > I'm getting a daily crash (call to fatalx). No clue what triggers it and
>> > the logging is really sparse. I couldn't follow what the code in
On 2021/10/01 14:43, Stuart Henderson wrote:
> On 2021/10/01 09:29, abyx...@mnetic.ch wrote:
> > I'm getting a daily crash (call to fatalx). No clue what triggers it and
> > the logging is really sparse. I couldn't follow what the code in ca.c is
> > actually doing (what the hash belongs to that
On 2021/10/01 09:29, abyx...@mnetic.ch wrote:
> I'm getting a daily crash (call to fatalx). No clue what triggers it and the
> logging is really sparse. I couldn't follow what the code in ca.c is actually
> doing (what the hash belongs to that is triggering the crash). A snip from
> /var/log/dae
I'm getting a daily crash (call to fatalx). No clue what triggers it and the
logging is really sparse. I couldn't follow what the code in ca.c is actually
doing (what the hash belongs to that is triggering the crash). A snip from
/var/log/daemon is reproduced below. There are no other log messag
