Comments on: Bash Tip: Closing File Descriptors http://blog.apokalyptik.com/2007/10/24/bash-tip-closing-file-descriptors/ The random things that spew forth from my brain... Mon, 16 Jan 2012 18:43:29 +0000 hourly 1 http://wordpress.org/?v=3.4-alpha-19620 By: apokalyptik http://blog.apokalyptik.com/2007/10/24/bash-tip-closing-file-descriptors/comment-page-1/#comment-10293 apokalyptik Mon, 21 Mar 2011 08:30:54 +0000 http://blog.apokalyptik.com/2007/10/24/bash-tip-closing-file-descriptors/#comment-10293 @foo Granted. But sometimes screen is not necessary or wanted. checking the PIDfile contents versus the running process list is, naturally, a good idea. But the post was about closing the file descriptors, not writing idfiles or killing processes, so the example is just that: an example. @foo Granted. But sometimes screen is not necessary or wanted. checking the PIDfile contents versus the running process list is, naturally, a good idea. But the post was about closing the file descriptors, not writing idfiles or killing processes, so the example is just that: an example.

]]> By: foo http://blog.apokalyptik.com/2007/10/24/bash-tip-closing-file-descriptors/comment-page-1/#comment-10292 foo Mon, 21 Mar 2011 02:16:45 +0000 http://blog.apokalyptik.com/2007/10/24/bash-tip-closing-file-descriptors/#comment-10292 why not just start up screen and while true;do sh myscript.sh; done ? then attach to the screen session if you ever want to close it. Then you don't ever have to worry about the PID getting recycled, and your script accidentally closing the wrong process! why not just start up screen and while true;do sh myscript.sh; done ?

then attach to the screen session if you ever want to close it. Then you don't ever have to worry about the PID getting recycled, and your script accidentally closing the wrong process!

]]> By: ndronen http://blog.apokalyptik.com/2007/10/24/bash-tip-closing-file-descriptors/comment-page-1/#comment-7919 ndronen Wed, 15 Oct 2008 08:20:17 +0000 http://blog.apokalyptik.com/2007/10/24/bash-tip-closing-file-descriptors/#comment-7919 Yeah, this is broken: exec 3>&- # close stdin exec 2>&- # close stdout exec 1>&- # close stderr It should be exec 0>&- # close stdin exec 1>&- # close stdout exec 2>&- # close stderr Yeah, this is broken:

exec 3>&- # close stdin

exec 2>&- # close stdout

exec 1>&- # close stderr

It should be

exec 0>&- # close stdin

exec 1>&- # close stdout

exec 2>&- # close stderr

]]> By: dandu http://blog.apokalyptik.com/2007/10/24/bash-tip-closing-file-descriptors/comment-page-1/#comment-7761 dandu Fri, 18 Apr 2008 10:57:00 +0000 http://blog.apokalyptik.com/2007/10/24/bash-tip-closing-file-descriptors/#comment-7761 hey, stdin is on fd 0 not 3 :) hey, stdin is on fd 0 not 3 :)

]]>