Summary: | sys-apps/openrc-0.10.5: [RC_PARALLEL] flock() failed: Interrupted system call | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pacho Ramos <pacho> |
Component: | [OLD] Core system | Assignee: | OpenRC Team <openrc> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | b+bugs.gentoo.org, e.suarezsantana, goeri.georg |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 439098 | ||
Attachments: |
rc.conf
Patch - retry flock if it was interrupted by signal |
Description
Pacho Ramos
2012-09-12 07:08:11 UTC
Created attachment 323578 [details]
rc.conf
Also happens for sys-apps/openrc-0.11.5 (which recently became marked as stable for amd64) Created attachment 337382 [details, diff]
Patch - retry flock if it was interrupted by signal
I'm sure that failing on any signal was not expected behavior. Rebooted many times with patched openrc, had no problems. Now, I don't see any error messages, and text isn't messed up. Sorry, but why this still isn't fixed? This bug isn't as important as crashing, but is very annoying. I can provide additional comments, if this will speed up the process: This bug is introduced by this commit: http://git.overlays.gentoo.org/gitweb/?p=proj/openrc.git;a=commit;h=6be8a0679b8d64ea5b99ea98839eab2ce129988b This part of commit message is wrong: "flock() would simply block till a previous lock has been released". flock() will also fail when any signal arrives, as almost all blocking calls will do. So when flock() failed with errno==EINTR, we should try again. This won't return bug #360013. I use patched openrc since my first message here, and I didn't find any regressions, only improvements. This has been applied in commit 970893a and will be part of openrc-0.12. Thanks for the report, and sorry this took so long to apply. |