• Andy Wilkinson's avatar
    Handle relative pid folder correctly in the launch script · 03deff9a
    Andy Wilkinson authored
    Previously, a relative PID folder was not handled correctly when
    running stop, status, or force_reload. This meant that a service
    could be started when configured to use a relative pid file, but
    then could not be stopped.
    
    The PID folder should be treated as relative to the service's jar
    file. This commit updates stop, status, and force_reload to push the
    jar file's directory so that this is now the case for those three
    commands.
    
    Closes gh-7092
    03deff9a
Name
Last commit
Last update
..
basic-launch.sh Loading commit data...
launch-with-multiple-command-line-arguments.sh Loading commit data...
launch-with-multiple-java-opts.sh Loading commit data...
launch-with-multiple-run-args.sh Loading commit data...
launch-with-relative-pid-folder.sh Loading commit data...
launch-with-single-command-line-argument.sh Loading commit data...
launch-with-single-java-opt.sh Loading commit data...
launch-with-single-run-arg.sh Loading commit data...
launch-with-use-of-start-stop-daemon-disabled.sh Loading commit data...
restart-when-started.sh Loading commit data...
restart-when-stopped.sh Loading commit data...
start-when-started.sh Loading commit data...
start-when-stopped.sh Loading commit data...
status-when-killed.sh Loading commit data...
status-when-started.sh Loading commit data...
status-when-stopped.sh Loading commit data...
stop-when-stopped.sh Loading commit data...
test-functions.sh Loading commit data...