From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset="us-ascii" Date: Tue, 01 Jul 2008 16:11:02 +0200 From: "Karl Reichert" In-Reply-To: <4869EF09.2060908@domain.hid> Message-ID: <20080701141102.247930@domain.hid> MIME-Version: 1.0 References: <20080626100340.308320@domain.hid> <20080630084032.317850@domain.hid> <4868E463.5080103@domain.hid> <20080701074558.317840@domain.hid> <4869EF09.2060908@domain.hid> Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] Problems with Threads and RTnet List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: xenomai@xenomai.org > >>> Forgot to close the socket when program finishes, this is why the > >>> second run always failed. Now it works :) > >>> > >>> I thought that the socket will be closed automatically when the > >>> program exits, as this is the case in POSIX?! Is there a reason why > >>> this is not done in RTnet? > >> RTDM should do it with Xenomai 2.4. Are you sure you are not using an > >> older version of the kernel-space support ? > > > > No, I'm using Xenomai 2.4.3 without any additional patches, so there is > no older version of kernel-space support installed. > > If you have a simple test program, I would be glade to cross-check here. > > Moreover, you could have a look at /proc/xenomai/rtdm/open_fildes before > and after closing your app. It should give an overview on all open > descriptors. If they are stalled after closing your RTnet app, this is > definitely a bug that has to be understood and fixed. > > Jan > After a deeper look I found out, that we are using Xenomai 2.3.2, not 2.4.x So the socket has to be manually closed. After doing so, /proc/xenomai/rtdm/open_fildes shows no more open descriptors. So everything is fine, thanks for your help! Karl -- von Karl Reichert