Am 24.09.2010 11:59, schrieb Steve Lane: > Update: while it is the case that backslash-escaping the forward > slashes in JAVA_OPTS in /etc/default/tomcat6 did allow the tomcat6 > package to configure successfully, it now means that the backslashes > are in the pathname in the command line, as reported by 'ps', like so > (the problem is at HeapDumpPath): > > # ps -fwwwu tomcat6 > UID PID PPID C STIME TTY TIME CMD > tomcat6 19698 1 11 02:48 ? 00:00:47 > /usr/lib/jvm/java-6-sun/bin/java > -Djava.util.logging.config.file=/var/lib/tomcat6/conf/logging.properties > -Djava.awt.headless=true -Xmx512m -XX:MaxPermSize=256m -XX:+UseParNewGC > -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled > -XX:+TraceClassLoading -XX:+TraceClassUnloading > -XX:HeapDumpPath=\/var\/log\/tomcat6\/java_pid_4.hprof > -XX:+HeapDumpOnOutOfMemoryError -Djava.net.preferIPv4Stack=true > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > -Djava.endorsed.dirs=/usr/share/tomcat6/endorsed -classpath > /usr/share/tomcat6/bin/bootstrap.jar -Dcatalina.base=/var/lib/tomcat6 > -Dcatalina.home=/usr/share/tomcat6 -Djava.io.tmpdir=/tmp/tomcat6-tmp > org.apache.catalina.startup.Bootstrap start
It works for me: tomcat6 7767 1 46 13:41 ? 00:00:05 /usr/lib/jvm/default-java/bin/java -Djava.util.logging.config.file=/var/lib/tomcat6/conf/logging.properties -Djava.awt.headless=true -Xmx128m -XX:+UseConcMarkSweepGC -XX:HeapDumpPath=/var/log/java_pid_4.hprof -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/usr/share/tomcat6/endorsed -classpath /usr/share/tomcat6/bin/bootstrap.jar -Dcatalina.base=/var/lib/tomcat6 -Dcatalina.home=/usr/share/tomcat6 -Djava.io.tmpdir=/tmp/tomcat6-tmp org.apache.catalina.startup.Bootstrap start May you run debconf-show tomcat6 please? Torsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
