Hello On Mon, Apr 25, 2011 at 10:03 AM, Albert Strasheim <[email protected]> wrote: > With systemd 25 I get: >> systemd[1]: Got invalid poll event on socket. > systemd[1]: foo.socket: Got invalid poll event (0x11) on socket.
I think I know what's going on here. My service that is consuming this socket is written in Go. Go currently has an issue where if you close a socket, it also calls shutdown on that socket. This has been discussed on the Go mailing list, but not fixed yet: http://groups.google.com/group/golang-dev/browse_thread/thread/c6ef223b67936f07 It seems this happens even for listen sockets, which causes an EPOLLHUP, which is 0x10. Maybe systemd needs to guard against this kind of "buggy" service behavior, where the service "cleans up" the socket that systemd has passed to it? Regards Albert _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
