I had the same problem - as suggested, backslash escaping the forward
slashes in the pathname solved it.
Thanks!
(Seems like it's still a bug, though.)
--
Steve Lane
System Administrator, Scientific Computing
Joint BioEnergy Institute
Lawrence Berkeley National Laboratory
--
To
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
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
I'm experiencing the same problem.
I have a path in javaopts (to work around a
braindead requirement of one of servlets I need to host).
My debconf entries are:
aquinas:~# debconf-show tomcat6
tomcat6/javaopts: -Djava.awt.headless=true -Xmx128M
-DPROTEI_DIR=/var/lib/tomcat6/webapps/rvom
# debconf-show tomcat6
* tomcat6/javaopts: -Djava.awt.headless=true -Xmx128m -Xmx512m
-XX:MaxPermSize=256m -XX:+UseParNewGC -XX:+CMSClassUnloadingEnabled
-XX:+CMSPermGenSweepingEnabled -XX:+TraceClassLoading -XX:+TraceClassUnloading
-XX:HeapDumpPath=\/var\/log\/tomcat6\/java_pid_4.hprof
Package: tomcat6
Version: 6.0.28-6
Severity: important
I tried to upgrade tomcat6 6.0.28-1 using tomcat6 6.0.28-6 which results in the
following error:
Setting up tomcat6 (6.0.28-6) ...
sed: -e expression #1, char 151: unknown option to `s'
dpkg: error processing tomcat6 (--configure):
Hi,
Am 23.09.2010 11:34, schrieb Adrian Zaugg:
Setting up tomcat6 (6.0.28-6) ...
sed: -e expression #1, char 151: unknown option to `s'
dpkg: error processing tomcat6 (--configure):
subprocess post-installation script returned error exit status 1
...
tomcat6/javaopts:
7 matches
Mail list logo
