Projects / Unix Mobile Agents

Unix Mobile Agents

Unix Mobile Agents is a generic, flexible, easy to use mobile agent architecture implemented in a set of bash scripts. This design is made to be trivial to deploy and setup. Agents can be configured to traverse the network in sorted order, in user defined order, or as a random walk. They can also run in a repeated loop, or in a single pass through the network. Connections are made via public-key SSH authentication, and the screen utility is used to allow agents to run without requiring terminals.

Operating Systems

Recent releases

  •  29 May 2005 10:54

    Release Notes: The local working directory for agents has been modified to guarantee no collisions when NFS mounts are being used to run agents. Users can now exclude hosts explicitly on the command line. was removed in lieu of an agent that installs UMA itself. Agents must now be shell scripts. This fixes a bug when an agent tried to influence what host would be hopped to next, resulting in a forking of agents. UMA now uses rsync to migrate, instead of 'scp'.

    •  22 Feb 2005 02:59

      Release Notes: This release added a "beaconing" capability that allows you to track the agents progress through the network. The beaconing is generic, and can be used from within agents to send arbitrary messages home. The method by which agents migrate was modified so that all tasking is pushed ahead of the final SSH call.

      •  18 Oct 2004 01:45

        Release Notes: The generic agent script now pulls from $0 the name of the agent to run, making agent_functions more generic, and usable by homemade agent scripts. An inter-agent messaging feature has been added, allowing agents to pass multi-line messages to each other on the agent PID level, or broadcast on the agent task level.

        •  03 Oct 2004 15:06

          Release Notes: This release adds some missions to do removal of abort files and resume waited agents. A spawnagent script has been added so that the agent doesn't always run on localhost just to migrate it somewhere else. It also allows you to guarantee the order in which things are executed. This means you also don't need to specify the current node for the first one; it figures it out itself. Validation is not performed when goto_host is called; it is done by hand in

          Recent comments

          17 Oct 2004 12:25 chrisdahn

          Next on tap
          Next on the list of features is a way to specify what nodes to run on in the agent network. This will be both inclusive and exclusive. Namely, given the definition of the agent network, only run on this subset, or run on everything but this subset.


          Project Spotlight


          A Fluent OpenStack client API for Java.


          Project Spotlight

          TurnKey TWiki Appliance

          A TWiki appliance that is easy to use and lightweight.