commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frank Gevaerts (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DAEMON-327) New -cwd default needlessly breaks backwards compatibility
Date Thu, 20 Nov 2014 13:52:34 GMT
Frank Gevaerts created DAEMON-327:
-------------------------------------

             Summary: New -cwd default needlessly breaks backwards compatibility
                 Key: DAEMON-327
                 URL: https://issues.apache.org/jira/browse/DAEMON-327
             Project: Commons Daemon
          Issue Type: Bug
          Components: Jsvc
    Affects Versions: 1.0.15
         Environment: debian/amd64
            Reporter: Frank Gevaerts
            Priority: Minor


Before 1.0.15, jsvc did not change working directory in any way, so the way to set the cwd
for an application was just to cd to the proper directory before calling jsvc.

Starting with 1.0.15, the -cwd option was added, which is indeed a useful addition.

However, 1.0.15 now *always* changes directory, with / as the default. This means that -cwd
now basically has to be used if a specific cwd is needed. Of course, -cwd is an invalid option
with
+versions before 1.0.15, so now it's impossible to make an init script that works with both
older and newer jsvc setups.

It's not clear to me why leaving the cwd as is if -cwd isn't used wasn't kept.

As an extra annoyance, -version doesn't work without also setting seemingly unrelated options,
so adding code to set -cwd based on jsvc version is harder than it should be.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message