[omniORB] SocketSetCloseOnExec and socket collection

[Sébastien Bouchex Bellomié]

Hi all,



Under linux (RH 4), I have some warnings like this :

File descriptor 3 left open

File descriptor 4 left open

...



They appear when our app (liked against omniorb) is spawning a child process. After a look at the omniorb code, it seems that SocketSetCloseOnExec is not called on the initial pipe created in tcpConnection::tcpConnection and in sslConnection:: sslConnection (the calling code is in SocketCollection::SocketCollection).



Is it a bug and is it done by design ?



Thanks

Seb



S?bastien BOUCHEX BELLOMI? - Senior Software Engineer
INFOVISTA SA
6, rue de la Terre De Feu
F-91952 Courtaboeuf Cedex
Tel : [phone] Fax : [phone]
***@infovista.com <mailto:***@infovista.com> http://www.infovista.com <http://www.infovista.com>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20070226/31fd18a6/attachment.htm

[Duncan Grisby]

Post by Sébastien Bouchex Bellomié
File descriptor 3 left open
File descriptor 4 left open
...
They appear when our app (liked against omniorb) is spawning a child
process. After a look at the omniorb code, it seems that
SocketSetCloseOnExec is not called on the initial pipe created in
tcpConnection::tcpConnection and in sslConnection:: sslConnection (the
calling code is in SocketCollection::SocketCollection).
Is it a bug and is it done by design ?

It's a bug. I've fixed it in CVS in the 4.1 development branch. Thanks
for the bug report.

Cheers,

Duncan.

[Sébastien Bouchex Bellomié]

Duncan,

Thanks for the fix !

Do you know when the new release is planned ?

Thanks
Seb

-------------------------------------------------------------------------------

Post by Sébastien Bouchex Bellomié
File descriptor 3 left open
File descriptor 4 left open
...
They appear when our app (liked against omniorb) is spawning a child
process. After a look at the omniorb code, it seems that
SocketSetCloseOnExec is not called on the initial pipe created in
tcpConnection::tcpConnection and in sslConnection:: sslConnection (the
calling code is in SocketCollection::SocketCollection).
Is it a bug and is it done by design ?

It's a bug. I've fixed it in CVS in the 4.1 development branch. Thanks
for the bug report.

Cheers,

Duncan.

[Duncan Grisby]

Post by Sébastien Bouchex Bellomié
Do you know when the new release is planned ?

I don't have any definite plans for an imminent release. I'll probably
release 4.1.1 in about a month.

Cheers,

Duncan.