peterkeen/proclaunch

Issues

• set_status_stopped_and_clean_pid_file never called

  #21 opened 14 years ago by mtowers
  1

• New command line option for log path

  #23 opened 14 years ago by peterkeen
  0

• Stops monitoring profiles under certain conditions

  #22 opened 14 years ago by peterkeen
  1

• Create a log_path setting file

  #19 opened 14 years ago by peterkeen
  1

• Fine-grained logging level command line option

  #20 opened 14 years ago by peterkeen
  1

• Clean up child process PID files on shutdown

  #17 opened 14 years ago by mtowers
  2

• Processes can be started but not stopped

  #15 opened 14 years ago by mtowers
  1

• Add kill_signal setting file

  #16 opened 14 years ago by peterkeen
  0

• An instance running as root will not be detected by instances running as normal users

  #18 opened 14 years ago by peterkeen
  1

• allow relative paths in pid_file

  #13 opened 14 years ago by peterkeen
  0

• strict mode

  #12 opened 14 years ago by peterkeen
  0

• Write a stats file into the state directory

  #11 opened 14 years ago by peterkeen
  0

• Multiple profile directories

  #10 opened 14 years ago by peterkeen
  0

• Multiple profile directories

  #9 opened 14 years ago by peterkeen
  0

• Exponential backoff on restart

  #8 opened 14 years ago by peterkeen
  0

• Proclaunch starts all profiles, even if profiles are already running (from previous run)

  #7 opened 14 years ago by thijsterlouw
  7

• proclaunch dies

  #4 opened 14 years ago by thijsterlouw
  17

• handle fork/exec for run not daemonizing

  #5 opened 14 years ago by peterkeen
  1

• Monitor proclaunch

  #6 opened 14 years ago by thijsterlouw
  1

• TESTS!

  #3 opened 14 years ago by peterkeen
  1

• Make sending SIGKILL optional

  #2 opened 14 years ago by peterkeen
  0

• Clean up Profile.pm

  #1 opened 14 years ago by peterkeen
  0