Re: seccomp violation (unexpected syscall 55)
Mantas MikulėnasSat Dec 12 13:41:39 2020
On Sat, Dec 12, 2020 at 12:19 AM Roy Marples <roy@xxxxxxxxxxxx> wrote:
> On 11/12/2020 22:14, Roy Marples wrote:
> > Hmmmm yes.
> > The attached patch allows this and should clean up the new hardware address:
> > null messages.
> > Let me know how it works for you.
> Wrong patch :)
> Scrub that and try this one please!
That seems to work. Now it just logs "route socket overflowed" a few
times (which is expected in this situation, I suppose) but otherwise
runs without problems.
Archive administrator: email@example.com