Affects Version/s: None
Fix Version/s: None
I think this is what's happening.
Basically, my script is using jack.input with the a specified ID so that jack.plumbing can auto connect the ports to the system captures. I've noticed quite often after Ctrl + C / SIGINT is sent to the process that if I try and start the script again it comes up with something like http://pastie.org/373616 which says it can't find a running jack instance. If I edit the ID in the script to something that hasn't used it's fine, likewise if I restart JACK it's fine. I don't seem to have this issue with other programs, but generally I have little control over their ID (it seems to be program name + PID) so I haven't been able to see if other programs have similar issues (and in which case JACK is not cleaning up).
I'm using JACK 0.116.1, the newest copy.
I found this is a little random, sometimes I can control + C with no issues. It happens probably 1 in 3 times.
Oddly enough, if I send SIGKILL, the issue doesn't seem to happen as much, out of about 15 goes it happened once, which is a lot less than pretty much every other time. Again SIGHUP seems to be similar in the since it doesn't happen as much.
If this is an issue with JACK, maybe you could do a quick hack and have an option to append the PID or something to the end of the channel name. Least it would work round the issue in the short term and still let me use jack.plumbing as it can do regular expression / pattern based rules.
This little annoyance would be great to sort out as it does bug me on my dev machine a lot.