Hello all,
I'm still getting these messages in my syslog in v2.0.3.
Maybe I missed something but I'm quite lost what to do
about this. I mean the only way for a script to leave
a file descriptor open is by having started a process
in the background and not redirecting its output/stderr/input
to /dev/null. In other words, how can a file descriptor
be left open, if there is no process attached to it?
Or, the other way around, if the script finishes
and all processes started by it have also terminated
there can not be any fd's left open???
Could all this be related to Bug #756
which is still open?
Peter
Peter Kruse wrote:
Hello,
In my logs I get these messages like this:
Feb 7 18:23:57 ha-test-1 lrmd: [2000]: info: RA output:
(rg1:fpbs1:start:stderr) Filedescriptor 3 left open File descriptor 4
left open File descriptor 5 left open File descriptor 6 left open File
descriptor 7 left open File descriptor 8 left open File descriptor 10
left open
Now I have two questions:
1. The message indicates that I have to make sure that all open files
are closed. Would it be enough to do this in the bash scripts:
exec < /dev/null > /dev/null 2>&1
Or would it be okay if when starting a process, to just do:
process < /dev/null > /dev/null 2>&1 &
2. If I don't make sure all filedescriptors are closed, will then
the open files persist until there are "too many open files"?
Could it be that this message is a result:
crm_attribute: [32702]: ERROR: socket_client_channel_new: socket: Too
many open files
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
