On Sat, 2014-09-20 at 13:05 +0200, Niels Peen wrote: > Another possible clue: I upgraded from ocserv 0.3 to 0.8 on September 15th. 0.3 has never caused this problem. I don't see much changes related to that issue from 0.3 to 0.8, but that looks like a race issue in the kernel and could be caused by different timings between calls. I've applied the suggested fix anyway as it looks correct. regards, Nikos
