Skip to content
This repository has been archived by the owner on Aug 20, 2024. It is now read-only.

Fix issue on with -errfile &1 being misinterpreted. #8

Merged
merged 1 commit into from
Jan 16, 2012
Merged

Fix issue on with -errfile &1 being misinterpreted. #8

merged 1 commit into from
Jan 16, 2012

Conversation

boxofrad
Copy link
Contributor

This commit fixes a weird issue i've been having where the &1 JSVC option would appear to be interpreted as:

Background the process & and run 1

And would return the following ouput:

[1] 992
Invalid Error File specified
Cannot parse command line arguments
1: command not found

This issue is present on Ubuntu 10.04 LTS and bash version 4.1.5(1).

calavera added a commit that referenced this pull request Jan 16, 2012
Fix issue on with -errfile &1 being misinterpreted.
@calavera calavera merged commit a5bbcba into trinidad:master Jan 16, 2012
@calavera
Copy link
Contributor

Thank you!! I'm releasing a new version of the gem with you patch right away.

@tolsen
Copy link

tolsen commented Sep 6, 2012

I'm having this issue now. The fix appears to have been reverted in c532ef5

@tolsen
Copy link

tolsen commented Sep 6, 2012

btw, I am also using Ubuntu 10.04 LTS with bash version 4.1.5(1)

@tolsen
Copy link

tolsen commented Sep 7, 2012

The problem appears to have mysteriously gone away. Not sure why, but I'll let you know if I find out!

@tolsen
Copy link

tolsen commented Sep 7, 2012

Ok. I think the problem is that I was running the full jsvc command by hand to debug a different problem. When run directly, you must put single quotes around &1. But when placed inside an environment variable (such as START_COMMAND in init.d/trinidad) and run through the environment variable, &1 is automatically escaped.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants