On 04/20/2013 08:16 AM, Frank Myhr wrote:
(Replying to self):
Work-around is to start syslog-ng with --no-caps. On Debian / Ubuntu,
this line should be in /etc/default/syslog-ng (make sure it's not
commented out):
SYSLOGNG_OPTS=--no-caps
I still think it's not ideal for CAP_FS_FREEZE to
The bug in question was fixed in kernel 042stab077.7, please give it a try.
On 04/12/2013 05:01 AM, Brad Alexander wrote:
Todd,
Thanks for responding. Actually, I did google for it, I guess I didn't
go down the list far enough to encounter this post.
Thanks,
--b
On Wed, Apr 10, 2013 at
On 04/15/2013 02:53 AM, Roman Haefeli wrote:
On Mon, 2013-04-15 at 11:14 +0200, Roman Haefeli wrote:
On one of our host nodes this problem even triggered a kernel panic and
thus killed all CTs running on that host. The problem could have been
mitigated if 'vzctl start' would not try to read
On 04/22/2013 01:30 PM, Kir Kolyshkin wrote:
On 04/15/2013 02:53 AM, Roman Haefeli wrote:
On Mon, 2013-04-15 at 11:14 +0200, Roman Haefeli wrote:
On one of our host nodes this problem even triggered a kernel panic and
thus killed all CTs running on that host. The problem could have been
