ezran (Justin Greer)
- Login: ezran
- Email: ruby-lang.org@justingreer.com
- Registered on: 12/09/2014
- Last sign in: 12/09/2014
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 1 | 1 |
Activity
12/11/2014
-
06:01 PM Ruby Bug #10583: Process.spawn stalls forever opening named pipes (fifo)
- While the reduced testcase I attached previously sounds like a rare usage, it's actually pretty common any time you're tying together multiple programs and one of them only knows how to work with a file/fifo instead of stdin/stdout. Our...
12/10/2014
-
- While open(2) blocks, the spawn should NOT block. Only the spawned process itself should block waiting on the open() - the parent process should continue, and should not require threads to make this happen.
Using the system calls dir...
12/09/2014
-
- Ruby's implementation of Process.spawn seems to attempt to send error/success information from the spawned process back to the parent, and the parent won't continue until it gets this information. However, a named pipe (fifo) is mapped ...