TODO.txt 2.3 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879
  1. - Web interface:
  2. - present status in addition to state (e.g. spawnerr, etc, same as
  3. supervisorctl)
  4. - provide "restart all" functionality
  5. - Documentation:
  6. - In nodaemon mode, child processes will be sent SIGINT when Ctrl-C
  7. is pressed.
  8. - Error conditions when X-bit not set on command file.
  9. - Unit test the http_client package.
  10. - Unit tests for meld classes and ui server.
  11. - Create named process log files after we setuid.
  12. - Usage messages when we invoke supervisord/supervisorctl -h
  13. - Tail main log.
  14. - Figure out how to test the actual supervisord class.
  15. - Test log rotation.
  16. - Command-line arg tests.
  17. - supervisorctl one-shot tests.
  18. - packaging.
  19. - test under py 2.3 to make setup.py assertions true
  20. - supervisorctl command history
  21. - test startup as root
  22. - stop logging all RPC requests in info mode when we ship
  23. - reopen child logs when we get a logreopen signal
  24. - Collector issue 75:
  25. If the pid file isn't writable, it dies silently. When I ran it with
  26. --nodaemon this became clear, but nothing about the error goes into
  27. the log file or console when daemonizing.
  28. - Collector issue 76:
  29. Adding -c to the shell script also drove me nuts for a while, since
  30. I got an error about two -c's. Maybe instead it could set an
  31. environmental variable in the shell script and read that for the
  32. default?
  33. - Collector issue 84:
  34. I'd like to make Paste detect when it is running under Supervisor,
  35. mostly so it would know that it could safely die to be
  36. restarted. Otherwise it starts its own monitoring process to handle
  37. restarts. I think always setting an environmental variable (e.g.,
  38. "SUPERVISOR_ENABLED") would be sufficient.
  39. - Collector issue 152:
  40. I'd like supervisor to look after a number of postgres instances
  41. (well, initially only 1, but I will need it to manage 3). The first
  42. difficulty I had was that the postgres start-up program (pg_ctl)
  43. takes an options param that it passes directly to the postmaster
  44. program it controls, which can contain several options that only
  45. the postmaster understands and it expects these to be in quotes so
  46. they are treated as a group, e.g pg_ctl -o "-p 4321 -h hostname -d
  47. datadir" but supervisor doesn't appear to preserve the quotes. In
  48. my case I only need the one option so I used -o "-p4321", as a
  49. workaround.