Hello all, I recently upgraded my Debian 'unstable' system (I know -- a terrible thing to do to a functioning system), including a recent version of the "jackd" package. jackd --version jackdmp 1.9.6 The package contains the utility program, jack_lsp, which I rely on and need to be able to parse. I find the STDOUT stream is peppered with what appear to be debugging messages from the JACK server. Is that purposeful or a bug? $ jack_lsp Jack: JackClient::SetupDriverSync driver sem in flush mode Jack: JackPosixSemaphore::Connect jack_sem.1000_default_lsp Jack: Already connected name = lsp Jack: Clock source : system clock via clock_gettime Jack: JackLibClient::Open name = lsp refnum = 2 system:capture_1 system:capture_2 system:playback_1 system:playback_2 Jack: jack_client_close Jack: JackClient::Close ref = 2 Jack: JackClient::Deactivate Jack: JackSocketClientChannel::Stop Jack: JackPosixThread::Kill Jack: JackClientSocket::Close Jack: JackClientSocket::Close Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_lsp Jack: JackLibClient::~JackLibClient Jack: JackShmReadWritePtr1::~JackShmReadWritePtr1 2 Jack: Succeeded in unlocking 120 byte memory area Jack: JackLibGlobals Destroy 8b67028 Jack: ~JackLibGlobals Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_system Jack: JackPosixSemaphore::Disconnect jack_sem.1000_default_freewheel Jack: no message buffer overruns Jack: JackPosixThread::Stop Jack: ThreadHandler: exit Jack: JackShmReadWritePtr::~JackShmReadWritePtr 1 Jack: Succeeded in unlocking 1012 byte memory area Jack: JackShmReadWritePtr::~JackShmReadWritePtr 0 Jack: Succeeded in unlocking 82213148 byte memory area Jack: jack_client_close res = 0 Regards, Joel -- Joel Roth _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
