25 Nov
2019
25 Nov
'19
6:19 p.m.
Log rotation is not what I could consider the "correct" solution. But
I guess it's what I have to do for now until a log-level control is
implemented. All the little things my application needs to take care of
on a users system is getting really complicated. I am of the opinion
that default log levels should be low, with the option to get more
verbose when the user is interested in the extra information only.
Good to know others folks are see this as a bug as well.
Thanks everyone.
Ethan...
On Sun, 2019-11-24 at 16:36 -0800, Len Ovens wrote:
On Sun, 24 Nov 2019, Ethan Funk wrote:
I am almost a week into testing my jack-audio
application with no
crashes ofjackd or my application. Bug abound (in my code), but
that is the point oftesting. Fixing as I go. I am using Ubuntu
Studio control to run jackd...actually jackdbus, which brings me to
my question:
How do I get control over jackdbus logging? I currently have an
gigantic log fileit is creating at ~/.log/jack/jackdbus.log from my
testing.
Yes I have this concern too. jackdbus is controled by using
jack_control or dbus directly for which there is no documentation
besides the source I would guess. US_controls uses jack_control right
now (which also has no documentation) and by running jack_control
with no parameters one gets a list of commands some of which will
tell you what some other commands might be. None of them that I could
find will set logging levels. The next version of US_controls will
use logrotate to help keep the log files from getting too big. You
may want to set up a cron job to do this for you until that release.
It would be possible to use jackd instead of jackdbus but that would
just mean the the US_controls log would start to grow quicker instead
because jackd logs to stdout and stderr.
So the answer is that while jackdbus seems to provide no way of doing
this, logroatate is already installed and gets run by cron once a day
(I think) by the system. However, because your log file is in
userland you would be better off running it from the user crontab
with it's own config file.
--Len Ovenswww.ovenwerks.net
_______________________________________________Linux-audio-dev
mailing listLinux-audio-dev(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev