Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't send signals #19

Open
fourteatoo opened this issue Dec 7, 2015 · 2 comments
Open

can't send signals #19

fourteatoo opened this issue Dec 7, 2015 · 2 comments

Comments

@fourteatoo
Copy link

Signals do not work, at least on OSX with goon:

iex(3)> proc = Porcelain.spawn("sleep", ["30"], [])
%Porcelain.Process{err: nil, out: :string, pid: #PID<0.153.0>}
iex(4)> Porcelain.Process.signal proc, 15
{:signal, 15}
iex(5)> Porcelain.Process.signal proc, :kill
{:signal, :kill}
iex(6)>

I still keep seeing the process:

$ ps axww | fgrep sleep
48681 ?? Ss 0:00.01 /usr/local/bin/goon -proto 2.0 -out -- /bin/sleep 30
48682 ?? S 0:00.00 /bin/sleep 30
48690 s007 S+ 0:00.00 fgrep sleep

@tokafish
Copy link

@fourtytoo I'm seeing something similar, and I'm not able to stop a process as well. Have you found any workaround to this?

@alco
Copy link
Owner

alco commented Feb 26, 2016

Hi folks. There's a bug in goon that prevents signals from being delivered, see alco/goon#6.

You should be able to work around it by providing some input to the spawned process, for example, in: "ignore me".

Unfortunately, I can't say when I'll be able to fix this. I have plans to release a new version of Porcelain with a bunch of fixes at some point, but no defined dates at this point.

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

No branches or pull requests

3 participants