Skip to content

Implemented fifo opening with retries.#9

Open
RomanShumkov wants to merge 1 commit intokriswallsmith:masterfrom
RomanShumkov:feature/fifoOpeningWithRetries
Open

Implemented fifo opening with retries.#9
RomanShumkov wants to merge 1 commit intokriswallsmith:masterfrom
RomanShumkov:feature/fifoOpeningWithRetries

Conversation

@RomanShumkov
Copy link
Contributor

fopen may fail temporarily (e.g. "failed to open stream: Interrupted system call" when there are 30+ forks).
It's critical to handle fifo opening errors because of blocking read in child. Child is waiting forever if no parent connects.

fopen may fail temporarily (e.g. "failed to open stream: Interrupted system call" when there are 30+ forks).
It's critical to handle fifo opening errors because of blocking read in child. Child is waiting forever if no parent connects.
@kriswallsmith
Copy link
Owner

Thanks for your work, @RomanShumkov. I'm curious why you have a different value passed to usleep() in this pull request and in #8? I'm also wondering if you think it's possible to write test coverage for this sort of thing.

@RomanShumkov RomanShumkov mentioned this pull request Mar 23, 2013
@RomanShumkov
Copy link
Contributor Author

These usleep() parameters gave me the best results during stress testing. By best results i mean lowest $retriesCounter values.
If someone has better suggestions for usleep() parameters or other implementations details, feel free to share.

Don't have much time for implementing tests at the moment. Maybe in nearest future.

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

Successfully merging this pull request may close these issues.

2 participants