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

Use Kernel.spawn instead of system #27

Open
jalcine opened this issue Apr 22, 2015 · 2 comments
Open

Use Kernel.spawn instead of system #27

jalcine opened this issue Apr 22, 2015 · 2 comments

Comments

@jalcine
Copy link

jalcine commented Apr 22, 2015

Just to prevent the holding up of Guard from running other guards; it'd be dope if this didn't use system but used Kernel.spawn instead.

@sethk
Copy link

sethk commented Jan 21, 2016

I would like to have this as well, and of course it would need to avoid running concurrently.

@jalcine
Copy link
Author

jalcine commented Jun 26, 2017

Ah so you'd want this to ensure serial execution of guards. That makes sense.

We could take that PID and then use Process.wait on it.

P.S: A year later! </3. I still use Guard a lot so this means a lot.

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

2 participants