Reputation
Top tag
Next privilege 100 Rep.
Edit community wikis
Badges
1 8
Impact
~6k people reached

  • 0 posts edited
  • 0 helpful flags
  • 2 votes cast
Jun
12
comment ansible: why is the file module skipping?
How is shell: chown not idempotent? You can run it as many times as you like, and the state of the machine is exactly the same as if you'd just run it once. That's idempotency, no?
Feb
24
comment Upstart script vs. command-line: why this difference in behavior?
Bingo! I thought I was able to successfully run this from the command line, but it turns out I could only run it from the command line when starting in places where the tomcat user has write access. Thanks!
Feb
22
comment Upstart script vs. command-line: why this difference in behavior?
Comparing env output, the upstart environment was missing several variables (including $USER and $HOME). But even adding all of these environment variables to upstart does not reproduce the success of a command-line call. I added an example of the error (one of many) to the post above. (+1 for the vimdiff recommendation, thanks)
Feb
19
comment Upstart script vs. command-line: why this difference in behavior?
@Nils: execs catalina.sh but exits immediately -- which prevents upstart from being able to stop the job later (unless I'm misunderstanding your suggestion).
Feb
18
comment Upstart script vs. command-line: why this difference in behavior?
I would like to understand why upstart breaks without it, given that on the command-line I can run catalina.sh via absolute path from anywhere. This is for my own understanding (since I'm obviously missing something about the environment upstart presents).
Feb
17
comment Upstart script vs. command-line: why this difference in behavior?
As I tried to ask in my question though: how come I can execute (on the command line) /opt/apache-tomcat-7.0.34/bin/catalina.sh run from anywhere, without chdiring, and things work fine? (Things only break when running from upstart without chdir).