But when running this program, the connection to the destination socket fails. The program exits after trying to connect to the destination socket with "cannot connect to network".
This must be a problem on your gnu/linux box. A quick paste&paste/compile/run showed no problem on my system. And, furthermore, the connect command on a UDP socket (in contrast to TCP) does not cause any control traffic between sender and receiver.
Is this to be expected, did we forget something obvious? Is the idea of combining non-realtime and real-time in this way reasonable? If not, are there other solutions for the goal we want to achieve?
It's reasonable if you are aiming for "better" real-time (i.e. improved soft real-time), and it is already successfully practiced by several RTnet users.
Jan
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ RTnet-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/rtnet-users
