On Mon, May 05, 2008 at 09:14:35PM +0200, [EMAIL PROTECTED] wrote: > Michael Koch wrote: > > On Mon, May 05, 2008 at 05:55:07PM +0200, [EMAIL PROTECTED] wrote: > > > Marcus Better wrote: > > > > > It seems like since I updated to tomcat5.5_5.5.26 I am having this > > > > > problem. > > > > > May 5 14:34:04 localhost jsvc.exec[7386]: check that your kernel > > > > > supports capabilities > > > > > > > > Does it? What does "grep CAPAB /boot/config-2.6.25-1-686" say? > > > > > > $ grep CAPAB /boot/config-2.6.25-1-686 > > > CONFIG_SECURITY_CAPABILITIES=y > > > CONFIG_SECURITY_FILE_CAPABILITIES=y > > > > And do you actually run that kernel? Does it work with an older kernel > > for you? > > > > Or mayby the kernel interface for that changed.. > > I think it is not linux kernel related because it also fails with > linux-image-2.6.24-1-686 and I remember to have the previous tomcat5.5_5.5.25 > running. > Looking at the logs seems that the installation of tomcat5.5_5.5.26 > caused it to stop running anymore, but I can not confirm it. > > Are you able to run an unmodified tomcat5.5_5.5.26 from unstable?
I run 5.5.26-2 (thats the version from unstable plus the classpath fix). It runs without problems here. Please give us the output of the two following commands to be sure: cat /proc/version grep CAPA /boot/config-`uname -r` Cheers, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]