https://bz.apache.org/bugzilla/show_bug.cgi?id=58626
--- Comment #5 from Michael Osipov <1983-01...@gmx.net> --- (In reply to Christopher Schultz from comment #2) > I'm +0 on this idea, but failing to quote is going to be a problem. > > Instead of using an unquoted value, you should use if/else to either run the > command with the wrapper, or run it without the wrapper. Having an if/else around would duplicate 15 lines for nothing. Unnecessary maintenance overhead. (In reply to Mark Thomas from comment #3) > Given the length of time other HP-UX users have been running Tomcat without > this issue this looks more like an HP-UX configuration / usage error than > something that needs to be fixed in the Tomcat scripts. I'd be glad to see a better solution but there is not better way -- yet. Even HP does this, so it must be a OS-specific issue. I did not say that the Tomcat scripts are broken. We just need to broaden support. OS X, OS/400 and Cygwin get special treatment too. (In reply to Konstantin Kolinko from comment #4) > You should be able to patch the script that calls catalina.sh to wrap that > call with a nohup. Such a recipe is already mentioned in the FAQ Not an option because "stop" does not work anymore. > https://wiki.apache.org/tomcat/TomcatOnSolaris10 > https://wiki.apache.org/tomcat/FAQ/Linux_Unix#Q3 Tomcat 5.5? This is ages old. Nothing is worse that outdated information. > It is also possible to consider switching from "catalina.sh start" to > "catalina.sh run". Not an option becuase it does not detach for the shell script and stdout/stderr go not to catalina.out. > In general, this is interesting. With nohup I have to redirect stdout and > stderr, or it will create its own nohup.out. Here the redirection is > already on the command line, so it writes to catalina.out without a need for > separate log file. > > > Note that there is also bug 53930 (allowing to replace catalina.out with a > pipe) that also intends to change the launch command. I think it is not > committed yet, because it is too tricky. > > > which turns: > > "$_RUNJAVA" "$LOGGING_CONFIG" $LOGGING_MANAGER $JAVA_OPTS $CATALINA_OPTS > > into > > $JAVA_WRAPPER "$_RUNJAVA" "$LOGGING_CONFIG" $LOGGING_MANAGER $JAVA_OPTS > > $CATALINA_OPTS > > 1. The above line is from Tomcat 6. It does not match catalina.sh in current > trunk which uses "eval". I am stuck for 6.x current but would be happy to see this fixed in 8.x and onwards. > 2. There are more that one variant of "start" command. There are different > commands with Security Manager enabled ("-security") and without one. My patch suggests patching both codepaths. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
