Tips On Managing Multiple Linux Processes

From The Player Project

Jump to: navigation, search
 
Line 1: Line 1:
-
 
-
 
Using Player with multiple robots, each with its own player server and set of clients, can be hard to manage, especially during development when you are frequently stopping, modifying, and starting multiple programs, often all on the same computer if using one of the simulators.
Using Player with multiple robots, each with its own player server and set of clients, can be hard to manage, especially during development when you are frequently stopping, modifying, and starting multiple programs, often all on the same computer if using one of the simulators.
Line 18: Line 16:
A long time ago I used MDNS service discovery to automate some of this. I'd run a Player server with Stage and several robots, and each robot had a device that issued a broadcast MDNS notification on the network, and MDNS listening daemons on different machines would run clients.  This made it easy to start up lots of clients, and distribute them on different computers.  I think the MDNS/Rendezvous code is still in Player but don't know if it's maintained -- I haven't used it or tested it in several years.
A long time ago I used MDNS service discovery to automate some of this. I'd run a Player server with Stage and several robots, and each robot had a device that issued a broadcast MDNS notification on the network, and MDNS listening daemons on different machines would run clients.  This made it easy to start up lots of clients, and distribute them on different computers.  I think the MDNS/Rendezvous code is still in Player but don't know if it's maintained -- I haven't used it or tested it in several years.
 +
 +
[[Category:Documentation]]

Latest revision as of 02:33, 31 January 2011

Personal tools