Re: Process Leak after using Session module
- From: Robert Klemme <shortcutter@xxxxxxxxxxxxxx>
- Date: Thu, 28 May 2009 20:45:04 +0200
On 28.05.2009 17:58, Tim Pease wrote:
On Wed, May 27, 2009 at 4:38 PM, Pra Bhandar <pbhandari2050@xxxxxxxxx> wrote:
Just a guess here, but try closing your oratab_file descriptor. The
bash shell will usually hang around if there are open file descriptors
or child processes running. If closing the file descriptor does not
work, then try looking for open sockets or running children.
oratab_file = Oratab()
File.open(oratab_file, 'r') do |ofile|
bash.execute ">instancestatus-output.txt"
ofile.each { |oratab_line|
...
}
end
Guessing here as well: maybe bash.close helps.
My 0.02 EUR...
robert
--
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/
.
- Follow-Ups:
- Re: Process Leak after using Session module
- From: Pra Bhandar
- Re: Process Leak after using Session module
- References:
- Process Leak after using Session module
- From: Pra Bhandar
- Re: Process Leak after using Session module
- From: Tim Pease
- Process Leak after using Session module
- Prev by Date: Re: Strange ruby-1.9.1 array substitution answer
- Next by Date: Re: Pythonic indentation (or: beating a dead horse)
- Previous by thread: Re: Process Leak after using Session module
- Next by thread: Re: Process Leak after using Session module
- Index(es):
Relevant Pages
|