1.0.2 or “Alpha 2” (Unreleased)

  • supervisorctl and supervisord no longer need to run on the same machinedue to the addition of internet socket support.
  • supervisorctl and supervisord no longer share a common configurationfile format.
  • supervisorctl now uses a persistent connection to supervisord(as opposed to creating a fresh connection for each command).
  • SRP (Secure Remote Password) authentication is now a supported formof access control for supervisord. In supervisorctl interactive mode,by default, users will be asked for credentials when attempting totalk to a supervisord that requires SRP authentication.
  • supervisord has a new command-line option and configuration fileoption for specifying “noauth” mode, which signifies that itshould not require authentication from clients.
  • supervisorctl has a new command-line option and configurationoption for specifying “noauth” mode, which signifies that itshould never attempt to send authentication info to servers.
  • supervisorctl has new commands: open: opens a connection to a newsupervisord; close: closes the current connection.
  • supervisorctl’s “logtail” command now retrieves log data fromsupervisord’s log file remotely (as opposed to reading itdirectly from a common filesystem). It also no longer emulates“tail -f”, it just returns lines of the server’s log file.
  • The supervisord/supervisorctl wire protocol now has protocol versioningand is documented in “protocol.txt”.
  • “configfile” command-line override -C changed to -c
  • top-level section name for supervisor schema changed to ‘supervisord’from ‘supervisor’
  • Added ‘pidproxy’ shim program.Known issues in alpha 2:
  • If supervisorctl loses a connection to a supervisord or if theremote supervisord crashes or shuts down unexpectedly, it ispossible that any supervisorctl talking to it will “hang”indefinitely waiting for data. Pressing Ctrl-C will allow youto restart supervisorctl.
  • Only one supervisorctl process may talk to a given supervisordprocess at a time. If two supervisorctl processes attempt to talkto the same supervisord process, one will “win” and the other willbe disconnected.
  • Sometimes if a pidproxy is used to start a program, the pidproxyprogram itself will “leak”.