Yeah, that's kind of ugly. I bet swift-init could block reading the new process's stdout. Then when it's closed either because the child exits or dups over its stdout fileno, the read should return.
-- low visibility of errors when using swift-init https://bugs.launchpad.net/bugs/639710 You received this bug notification because you are a member of Registry Administrators, which is subscribed to OpenStack Object Storage (swift). _______________________________________________ Mailing list: https://launchpad.net/~registry Post to : [email protected] Unsubscribe : https://launchpad.net/~registry More help : https://help.launchpad.net/ListHelp
