I guess I spoke too soon...

# supervisorctl
unix:///tmp/supervisor.sock no such file
supervisor>

It's pretty confusing, because it depends on what path I'm in when I run
supervisorctl. That's from my home directory. If I run it anywhere else:

# supervisorctl
**             RUNNING    pid 14982, uptime 10 days, 0:51:17
**             RUNNING    pid 26816, uptime 15:21:34
**             RUNNING    pid 14984, uptime 10 days, 0:51:17
**             RUNNING    pid 14986, uptime 10 days, 0:51:17
**             RUNNING    pid 6662, uptime 15:20:35
**             RUNNING    pid 14987, uptime 10 days, 0:51:17
supervisor>

TC

Reply via email to