11 Mar
2012
11 Mar
'12
1:59 p.m.
https://bugzilla.balabit.com/show_bug.cgi?id=161 --- Comment #3 from Balazs Scheidler <bazsi@balabit.hu> 2012-03-11 14:59:03 --- is it possible that the syslog-ng you are running is writing to some kind of destination that might stuck (and perhaps doesn't support non-blocking I/O)? The writev() call is only issued once (so busy looping over writev is not likely), the arguments seem to be sane. It should definitely return in a couple of minutes at most. Are all your core files sitting in writev() or there are differences? -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.