Wed May 13 13:41:53 CEST 2015
Still experiencing weirdnesses though.
My upstart script is:
exec bin/myapp foreground > /dev/null 2>&1
When I start to attach to the app's node, I get:
$ /usr/local/myapp/bin/myapp attach
Can't access pipe directory /tmp//usr/local/myapp/: No such file or
However, if I start my app manually:
$ /usr/local/myapp/bin/myapp start
Then everything works fine:
$ /usr/local/cometa/bin/cometa attach
Attaching to /tmp//usr/local/myapp/erlang.pipe.1 (^D to exit)
Can some kind soul explain to me what is going on?
On Tue, May 12, 2015 at 8:44 PM, Roger Lipscombe <roger@REDACTED>
> On 12 May 2015 at 18:45, Roberto Ostinelli
> <roberto.ostinelli@REDACTED> wrote:
> > Right. Unfortunately I can't find a way to oass this pid to the original
> script that starts it (using upstart).
> We use relx-generated releases with upstart. Simply run "bin/myapp
> foreground" from the upstart script.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions