-
Notifications
You must be signed in to change notification settings - Fork 274
wait for exclusive fds properly #830
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
Conversation
0e45a20 to
1e6b8e7
Compare
1e6b8e7 to
1cafa17
Compare
3eed883 to
fb3c6f9
Compare
844d529 to
75faaf3
Compare
N-R-K
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The poll part of the changes look much better now.
Will review and test the rest of the changes sometime this week.
1259a42 to
57b472c
Compare
3490c8b to
65d07dc
Compare
|
okay so, the changes to the dependency code can have some racy edge cases as it was, so i'll drop them for now and work on them again at a later date so for now, let's just get the refactors for proper waiting in |
it makes no sense for the parent to hold the lock, even with cloexec, and that makes attempts to wait on flock useless. it only worked so far due to busy-polling with open, so basically, we were waiting for an unlink, not a lockfile.
and use alarm.2 for timing out, this means that instead of waking up every 20ms and doing a few syscalls to check the lockfile, we wake up only every 10s for warning about the timeout
65d07dc to
7069e8c
Compare
exec_serviceopenrcwith the codepath ofrc-service, and i think that allows for better parallelism (not sure, need to test some more)