Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.
If a server 'falls', connections are maintained, but not detected by a new server instance. Is it technically possible for a yarp server to detect existing ports? Is there any reason for this not to be implemented?
Hi jcgvicto, there's an experimental name server that maintains port information in a persistent database, see these emails:
It isn't enabled by default yet, you need to choose to compile it as descibed in the email.
It would also be possible to detect ports via scanning as you suggest. I don't know of anyone who has done this.
Hello, and thank you for your quick reply. Yarpserver3 and --persist option work perfectly on local machine. External connections connect to nameserver (/root). However, connections with or between ports on a machine that is not running the server are not possible (not even nonpersistent). Am I missing some type of command?
Interesting, can you describe in more detail what happens when you try to make connections between ports on a machine that is not running the server? Sounds like there could be a bug. If you could report the output of running the following commands (from different terminals, on a machine not running the name server) that would be great:
yarp read /test
yarp name query /root
yarp name query /test
/sbin/ifconfig (or the equivalent for your OS, anything that shows your IP)
Ok, got things working. Maybe discovered a very minor bug (will post bug section) present in yarp2 too. Yarp3 is looking really good, cheers!
>> It would also be possible to detect ports via scanning as you suggest. I
don't know of anyone who has done this.
Maybe just include a possible feature of passing persistent database to other machines in the network?