Getting messages from already running jackd

[Patrick Shirkey]

Hi,

Is there a way to access the jack messages from an already running jackd?

For example if I had a jackd running in a x session but wanted to see
what was happening from a terminal.


Cheers.

--

Patrick Shirkey
Boost Hardware Ltd

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

[Ralf Mardorf]

Patrick Shirkey wrote:
> Hi,
>
> Is there a way to access the jack messages from an already running jackd?
>
> For example if I had a jackd running in a x session but wanted to see
> what was happening from a terminal.
>
>
> Cheers.

Launch QjackCtl or Qtractor, I guess they will display the same messages
+ the time when it occurred, that would be displayed by a terminal. I
never compared those messages, because I always run jackd manually in a
terminal and I only read the messages in the terminal.
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

[Nedko Arnaudov]

Ralf Mardorf <ralf.mardorf@...> writes:

> Patrick Shirkey wrote:
>> Hi,
>>
>> Is there a way to access the jack messages from an already running jackd?
>>
>> For example if I had a jackd running in a x session but wanted to
>> see what was happening from a terminal.
>>
>>
>> Cheers.
>
> Launch QjackCtl or Qtractor, I guess they will display the same
> messages + the time when it occurred, that would be displayed by a
> terminal. I never compared those messages, because I always run jackd
> manually in a terminal and I only read the messages in the terminal.

In case of autolaunching, jackd messages go to the terminal of the
application that launched it. With jackdbus, they always go to
~/.log/jack/jackdbus.log

Adding log file to jackd is trivial but it will break all those apps
that rely on jackd. For example qjackctl will have to be made to fetch
jackd messages from the jackd log file and not from jackd output pipes
(stdout/stderr).

--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>


_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

[James Warden]

something really not full-proof:

write a script like:

----------------------
#!/bin/sh

binprog=`which jackd.bin`
args=$*

if test -x $binprog; then
   $binprog $args >& $HOME/.jackd.log
fi
----------------------

save it into a file called jackd

then, as root:

# move the real jackd to jackd.bin

sudo mv /path/to/real/jackd /path/to/real/jackd.bin (replace /path/to/real by /usr/bin or /usr/local/bin if you usually run it from /usr/local)

# mv the script you just wrote to the install dir
sudo mv jackd /path/to/real/jackd

#make it executable
sudo chmod 755 /path/to/real/jackd

you should now be able to start up jack as usual but now, it will create a log file $HOME/.jackd.log that you can always check with
tail -f ~/.jackd.log


This is of course crude but it would sort of work.

Cheers,
J.



--- On Thu, 9/3/09, Nedko Arnaudov <nedko@...> wrote:

> From: Nedko Arnaudov <nedko@...>
> Subject: Re: [Jack-Devel] Getting messages from already running jackd
> To: "Ralf Mardorf" <ralf.mardorf@...>
> Cc: "Jack devel" <jack-devel@...>
> Date: Thursday, September 3, 2009, 7:36 AM
> Ralf Mardorf <ralf.mardorf@...>
> writes:
>
> > Patrick Shirkey wrote:
> >> Hi,
> >>
> >> Is there a way to access the jack messages from an
> already running jackd?
> >>
> >> For example if I had a jackd running in a x
> session but wanted to
> >> see what was happening from a terminal.
> >>
> >>
> >> Cheers.
> >
> > Launch QjackCtl or Qtractor, I guess they will display
> the same
> > messages + the time when it occurred, that would be
> displayed by a
> > terminal. I never compared those messages, because I
> always run jackd
> > manually in a terminal and I only read the messages in
> the terminal.
>
> In case of autolaunching, jackd messages go to the terminal
> of the
> application that launched it. With jackdbus, they always go
> to
> ~/.log/jack/jackdbus.log
>
> Adding log file to jackd is trivial but it will break all
> those apps
> that rely on jackd. For example qjackctl will have to be
> made to fetch
> jackd messages from the jackd log file and not from jackd
> output pipes
> (stdout/stderr).
>
> --
> Nedko Arnaudov <GnuPG KeyID: DE1716B0>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Jack-Devel mailing list
> Jack-Devel@...
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>

     
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org