<html dir="ltr"><head></head><body style="text-align:left; direction:ltr;"><div>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.</div><div><br></div><div>Good to know others folks are see this as a bug as well.</div><div><br></div><div>Thanks everyone.</div><div><br></div><div>Ethan...</div><div><br></div><div>On Sun, 2019-11-24 at 16:36 -0800, Len Ovens wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>On Sun, 24 Nov 2019, Ethan Funk wrote:</pre><pre><br></pre><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>I am almost a week into testing my jack-audio application with no crashes of</pre><pre>jackd or my application. Bug abound (in my code), but that is the point of</pre><pre>testing. Fixing as I go. I am using Ubuntu Studio control to run jackd...</pre><pre>actually jackdbus, which brings me to my question:</pre><pre><br></pre><pre>How do I get control over jackdbus logging? I currently have an gigantic log file</pre><pre>it is creating at ~/.log/jack/jackdbus.log from my testing.</pre></blockquote><pre><br></pre><pre>Yes I have this concern too. jackdbus is controled by using jack_control </pre><pre>or dbus directly for which there is no documentation besides the source I </pre><pre>would guess. US_controls uses jack_control right now (which also has no </pre><pre>documentation) and by running jack_control with no parameters one gets a </pre><pre>list of commands some of which will tell you what some other commands </pre><pre>might be. None of them that I could find will set logging levels. The next </pre><pre>version of US_controls will use logrotate to help keep the log files from </pre><pre>getting too big. You may want to set up a cron job to do this for you </pre><pre>until that release. It would be possible to use jackd instead of jackdbus </pre><pre>but that would just mean the the US_controls log would start to grow </pre><pre>quicker instead because jackd logs to stdout and stderr.</pre><pre><br></pre><pre>So the answer is that while jackdbus seems to provide no way of doing </pre><pre>this, logroatate is already installed and gets run by cron once a day (I </pre><pre>think) by the system. However, because your log file is in userland you </pre><pre>would be better off running it from the user crontab with it's own config </pre><pre>file.</pre><pre><br></pre><pre><br></pre><pre>--</pre><pre>Len Ovens</pre><a href="http://www.ovenwerks.net"><pre>www.ovenwerks.net</pre></a><pre><br></pre><pre>_______________________________________________</pre><pre>Linux-audio-dev mailing list</pre><a href="mailto:Linux-audio-dev@lists.linuxaudio.org"><pre>Linux-audio-dev@lists.linuxaudio.org</pre></a><pre><br></pre><a href="https://lists.linuxaudio.org/listinfo/linux-audio-dev"><pre>https://lists.linuxaudio.org/listinfo/linux-audio-dev</pre></a><pre><br></pre></blockquote></body></html>