Package: supervisor
Version: 3.0a8-1.1
Severity: important
Dear Maintainer,
* What led up to the situation?
running supervisorctl with a stock base config
* What exactly did you do (or not do) that was effective (or
ineffective)?
base config (same as my config) has:
serverurl=unix:///var/run//supervisor.sock ; use a unix:// URL for a unix
socket
* What was the outcome of this action?
unix:///tmp/supervisor.sock no such file
supervisorctl does not run
* What outcome did you expect instead?
supervisorctl should run, it must have a hardcoded path
for the moment, i ln -s'd the sock to /tmp
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/24 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages supervisor depends on:
ii python 2.7.3~rc2-1
ii python-medusa 1:0.5.4-7
ii python-meld3 0.6.5-3.1
ii python-pkg-resources 0.6.24-1
ii python-support 1.0.15
supervisor recommends no packages.
supervisor suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
