Johannes Schindelin wrote:
>On Tue, 29 Apr 2008, Andreas Ericsson wrote:
>> What syslogd are you using? Perhaps it insists on re-creating the
>> socket. That might cause the behaviour you're seeing, but then you
>> should probably see it in a ton of other daemons as well.
Recreating the socket should not cause this to happen either, because
the git-daemon will still hold on to the old inode (even after the file
has been removed).
>This is sysklogd from Ubuntu, compiled for amd64. The timestamp on
>/dev/log is older than a month.
I'd still recommend trying to reproduce the problem, then find out which
filedescriptor/file the close is hanging on.
--
Sincerely, srb@xxxxxxx
Stephen R. van den Berg.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
