-
Notifications
You must be signed in to change notification settings - Fork 33
pman overview
pman manages processes, i.e. programs or applications that are run by an underlying system. For the most part, these processes are command line applications (i.e. have no GUI) and usually do not interact really with a user at all. The purpose of pman is to provide other software agents the ability to execute processes via http and then be able to respond to these agents when queried about the process. In the simplest case, pman is given some string text that is the command line of the program to run on an underlying system shell. This program is executed, and pman can then be asked for information about this process.
See the main page here.
See the startup docs here.
To run a process, see here.
To search for a process, see here.
pman maintains a human-friendly/readable database of jobs and history, typically in the /tmp/pman directory of the machine on which it is run.
REST purists will note that communicating with pman is not pure REST, but rather REST-like. For example, querying pman is almost always done with POST requests as opposed to using GET verbs. The reason for this is partially historical and partially expedience. Information between the server and client is communicated in a JSON message payload and not really the http URL.
Since translating the current packet/payload scheme into URL type format should be straightforward, future versions of pman are projected to be more fully REST compliant.
--30--