Issue #5723 has been updated by Motohiro KOSAKI.


One question. Why don't you use /dev/null? Which behavior did you expected?

Thank you.

----------------------------------------
Bug #5723: Ruby fails when standard input is closed  
http://redmine.ruby-lang.org/issues/5723

Author: Randal Moore
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 1.9.3
ruby -v: ruby 1.9.3p0 (2011-10-30 revision 33570) [i686-linux]


If the ruby process is launched with its standard input closed, it does not behave very well.  The following output was logged by the ruby process under these circumstances.  The attached source file can be used to produce a minimal executable that duplicates the issue.  Note that this appears to be something that changed between 1.9.2 and 1.9.3.

[BUG] rb_update_max_fd: invalid fd (0) given.
ruby 1.9.3p0 (2011-10-30 revision 33570) [i686-linux]

-- Control frame information -----------------------------------------------
c:0001 p:---- s:0002 b:0002 l:000001 d:000001 TOP


-- C level backtrace information -------------------------------------------
-e [0x8173762]
-e [0x81b7de8]
-e(rb_bug+0x35) [0x81b7e85]
-e [0x8073427]
-e [0x8079be0]
-e [0x806da5a]
-e(ruby_init+0x97) [0x805b317]
-e [0x8058887]
/lib/libc.so.6(__libc_start_main+0xdc) [0x3cedec]
-e [0x8058781]

-- Other runtime information -----------------------------------------------

0: can't convert false into String (TypeError)



-- 
http://redmine.ruby-lang.org