-
Notifications
You must be signed in to change notification settings - Fork 15
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
Worker and pcntl_exec support #11
Comments
I'm not familiar with how pcntl_exec works. Have you tried to use it within your daemon yet? If you call that method while in a worker process, it might not cause any issues. But, since pcntl_exec "replaces" the current process with the sub process, I'm not sure what side effects that will have on the worker process, it may break it's communication with the parent daemon process. |
I will also add, that if you're just triggering a worker to 'fire and forget' the process, then you should be able to maybe safely use a Task, since those don't communicate to the daemon parent. |
and is it possible to retrieve Task exit code ? |
I've a somewhat handmade daemon using fork and pcntl_exec() but not with your Daemon yet |
If you use a Worker, then you can return the exit code, but not from a Task. |
crap I'm stuck ... |
That is why there are Workers. |
I mean the low level could be an event |
The |
I use pcntl_exec to isolate curl calls because curl is not multi process safe.
I was wondering how I could use php-daemon and workers and be able to handle the return code of the code ran under pcntl_exec()
The text was updated successfully, but these errors were encountered: