Bug#700377: Processed: reopen 700377

'supervisord.conf', 'etc/supervisord.conf', '/etc/supervisor/supervisord.conf', '/etc/supervisord.conf'] 2013/8/9 Debian Bug Tracking System : > Processing commands for cont...@bugs

Bug#700377: problem has re-occurred

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 ** RUNNINGpid 14982,

Bug#700377: supervisorctl has hardcoded sock path in /tmp

tags 700377 + unreproducible thanks hello, thanks for reporting. Could you please paste your complete configuation file, because, on the default configuration, it's not reproducible. And no code shows the sock path is hard coded. I'm tagging this bug to unreproducible. If it is reproducible,

Bug#700377:

I can't quite understand what you mean. I checked the code that supervisor hasn't hard coded socket path. It's read from the configuation. and supervisorctl has a default value of serverurl if there isn't a configuation file found. Could you please explain more clearly ? for example, paste your

Bug#700377: supervisorctl has hardcoded sock path in /tmp

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: serverur