Comments on: Do not close stderr http://bashcurescancer.com/do-not-close-stderr.html Learn the UNIX/Linux command line Mon, 06 Jun 2011 01:35:32 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: The best in command line xml: XMLStarlet http://bashcurescancer.com/do-not-close-stderr.html/comment-page-1#comment-13129 The best in command line xml: XMLStarlet Tue, 24 Jun 2008 04:33:23 +0000 http://bashcurescancer.com/?p=148#comment-13129 [...] Do not close stderr [...] [...] Do not close stderr [...]

]]> By: Noname http://bashcurescancer.com/do-not-close-stderr.html/comment-page-1#comment-6686 Noname Fri, 25 Apr 2008 20:22:23 +0000 http://bashcurescancer.com/?p=148#comment-6686 Which has started the whole ordeal as an uglu and a bad thing ... :) Which has started the whole ordeal as an uglu and a bad thing … :)

]]> By: Brock Noland http://bashcurescancer.com/do-not-close-stderr.html/comment-page-1#comment-6608 Brock Noland Thu, 24 Apr 2008 13:07:19 +0000 http://bashcurescancer.com/?p=148#comment-6608 Yep. Yep.

]]> By: Noname http://bashcurescancer.com/do-not-close-stderr.html/comment-page-1#comment-6602 Noname Thu, 24 Apr 2008 09:55:56 +0000 http://bashcurescancer.com/?p=148#comment-6602 Than the logical solution is 2>/dev/null ? Than the logical solution is 2>/dev/null ?

]]> By: Brock Noland http://bashcurescancer.com/do-not-close-stderr.html/comment-page-1#comment-6569 Brock Noland Wed, 23 Apr 2008 16:07:37 +0000 http://bashcurescancer.com/?p=148#comment-6569 <b>Naveed</b>: <i>Is that what happened?</i> Yep. <b>Brendan Miller</b>: <i>Cool, but since you’re using ansi c streams as opposed to unix file io isn’t this a bug in glibc? Shouldn’t glibc be checking to see if the file descriptor is open before fdopening file descriptor 2?</i> I am 99.9% sure UNIX file io would do the same thing. Naveed: Is that what happened?

Yep.

Brendan Miller: Cool, but since you’re using ansi c streams as opposed to unix file io isn’t this a bug in glibc? Shouldn’t glibc be checking to see if the file descriptor is open before fdopening file descriptor 2?

I am 99.9% sure UNIX file io would do the same thing.

]]> By: Brendan Miller http://bashcurescancer.com/do-not-close-stderr.html/comment-page-1#comment-6546 Brendan Miller Wed, 23 Apr 2008 08:15:52 +0000 http://bashcurescancer.com/?p=148#comment-6546 Cool, but since you're using ansi c streams as opposed to unix file io isn't this a bug in glibc? Shouldn't glibc be checking to see if the file descriptor is open before fdopening file descriptor 2? Cool, but since you’re using ansi c streams as opposed to unix file io isn’t this a bug in glibc? Shouldn’t glibc be checking to see if the file descriptor is open before fdopening file descriptor 2?

]]> By: forcey http://bashcurescancer.com/do-not-close-stderr.html/comment-page-1#comment-6545 forcey Wed, 23 Apr 2008 07:22:41 +0000 http://bashcurescancer.com/?p=148#comment-6545 That's really the case. The reason is that stderr is opened with fd=2 by default, and if you close it, the file descriptor you open next will be 2. And if you or some external program you called by system() produces error message to 'stderr' - your file would be corrupted. It actually happened to me. If you don't want your program to show error messages on the screen, please reopen stderr to somewhere else, rather than close it. That’s really the case. The reason is that stderr is opened with fd=2 by default, and if you close it, the file descriptor you open next will be 2. And if you or some external program you called by system() produces error message to ‘stderr’ – your file would be corrupted. It actually happened to me. If you don’t want your program to show error messages on the screen, please reopen stderr to somewhere else, rather than close it.

]]> By: Naveed http://bashcurescancer.com/do-not-close-stderr.html/comment-page-1#comment-6544 Naveed Wed, 23 Apr 2008 06:44:44 +0000 http://bashcurescancer.com/?p=148#comment-6544 Whoa, it seems like stderr was redirected to stdout since stderr was closed. Is that what happened? Whoa, it seems like stderr was redirected to stdout since stderr was closed. Is that what happened?

]]>