I'm also working on very similar requirements in
and like you two, I have to rely on a combination of open_port with
its constituent events and os:cmd/1 in order to SIGHUP/SIGKILL which
feels rather 'hackish' to me. I've also noticed that it makes consumer
code rather timing dependent, which is frustrating.
I would be willing to participate in either
(a) improving the built in port functionality or
Although C I'm fairly comfortable with, but C++ (which erlexec appears
1. cli clients my code launches can be 'detached' (usually erlang
So erlexec does sound promising, but IMO it would be *better* if the
On 26 May 2012 13:12, Gleb Peregud <glebe...@gmail.com> wrote:
> On Sat, May 26, 2012 at 11:06 AM, Benoit Chesneau <bchesn...@gmail.com> wrote:_______________________________________________
>> I'm trying to find a way to manage some os processes launched from
>> Erlang. For example I need to relaunch them when the external process
>> die for an unknown reason or send an HUP signal or just stop the
>> external process.
> Hello Benoit
> Looks like there are two of us, who needs a better mechanism to manage
> Maybe we could reanimate erlexec together?
erlang-questions mailing list
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.