On Thu, May 5, 2011 at 11:33, Kay Sievers <kay.sievers@xxxxxxxx> wrote: > On Thu, May 5, 2011 at 10:33, Johannes Schauer <j.schauer@xxxxxxxx> wrote: >> basically it's these two messages repeating infinitely: >> >> [pid 2353] epoll_wait(0xb, 0xbeb4d3b8, 0x8, 0xbb8) = 1 >> [pid 2353] SYS_366(0x4, 0, 0, 0x80000, 0) = -1 ENOSYS (Function not implemented) > > That's a syscall number and accept4(). It should be there since kernel > 2.6.28 and glibc 2.10. > > With proper kernel support, and a more recent strace it would look like: > Âaccept4(3, 0, NULL, SOCK_CLOEXEC)    = 11 > > Not sure how that can happen on your side. The last parameter, the > CLOEXEC flag is definitely not 0. Ah, no counted wrong, missed that there are 5 arguments. The 4th argument, the 0x80000 is the SOCK_CLOEXEC. So it looks like your kernel does not support accept4. Is that really a 2.6.32 kernel? Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
