[ https://issues.apache.org/jira/browse/DAEMON-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Thomas resolved DAEMON-297. -------------------------------- Resolution: Fixed Fix Version/s: 1.1.1 The check for "/" is not validation. Logically, such a request makes no sense. If the path to the executable is invalid, the executable won't run and the debug logging will never be seen. argv[0] has been added to the debug output. > Show jsvc path in debug output > ------------------------------ > > Key: DAEMON-297 > URL: https://issues.apache.org/jira/browse/DAEMON-297 > Project: Commons Daemon > Issue Type: Improvement > Reporter: Sebb > Priority: Minor > Fix For: 1.1.1 > > > From a question on the user list: > {code} > $ jsvc -jvm server -debug -home /usr/lib/jvm/java-6-openjdk -cp > commons-daemon-1.0.15.jar:api-monitor.jar ApiMonitorDaemon > +-- DUMPING PARSED COMMAND LINE ARGUMENTS -------------- > | Detach: True > | Show Version: No > | Show Help: No > | Check Only: Disabled > | Stop: False > | Wait: 0 > | Run as service: No > | Install service: No > | Remove service: No > | JVM Name: "server" > | Java Home: "/usr/lib/jvm/java-6-openjdk" > | PID File: "/var/run/jsvc.pid" > | User Name: "null" > | Extra Options: 1 > | "-Djava.class.path=commons-daemon-1.0.15.jar:api-monitor.jar" > | Class Invoked: "ApiMonitorDaemon" > | Class Arguments: 0 > +------------------------------------------------------- > ... > JSVC re-exec requires execution with an absolute or relative path > {code} > Note that the jsvc path is not part of the debug output; it should be, given > that it is validated. > The validation result could also be shown in the debug output, for example: > {code} > | JSVC path: "jsvc" : path error - must contain / > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)