Re: [LAD] jackdbus log controls?
While your correct that changing my approach to make use of pre- allocated players that are re-load-able would work for fixing the verbose log problem, it is a rather large design philosophy change to make this late in the design. The OS X version I am porting from had the media handling "builtin" using a similar, pre-allocated object approach. My new design is a departure form the original approach since I wanted to make the most use of jack's inter-application flexibility. Since I am at the testing stage at this point, a lot of re-coding would be needed to go back to the old, pre-allocated player approach. And I am kind of attached to leaving my core mixer inputs open/disconnected when not used my the automation algorithm, so they can be connected to sources by the user if they want. For now, I'll rotate log files. Thanks, Ethan... On Sat, 2019-11-30 at 13:19 +0100, Fons Adriaensen wrote: > On Sun, Nov 24, 2019 at 03:51:04PM -0700, Ethan Funk wrote: > i > > My application is endlessly forking new audio player processes that > > connect back to a core mixer via jack, play when needed, then > > disconnect when finished. So the above log file is crammed full of > > jack port connect and disconnect notices. How do I make it stop? > > Not really answering you questions, but avoiding the problem > that triggers it: just use a fixed set of players and control > them (load, stop, start, locate,...) instead of creating a new > player for each file... > > Ciao, > signature.asc Description: This is a digitally signed message part ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] jackdbus log controls?
On Sun, Nov 24, 2019 at 03:51:04PM -0700, Ethan Funk wrote: i > My application is endlessly forking new audio player processes that > connect back to a core mixer via jack, play when needed, then > disconnect when finished. So the above log file is crammed full of > jack port connect and disconnect notices. How do I make it stop? Not really answering you questions, but avoiding the problem that triggers it: just use a fixed set of players and control them (load, stop, start, locate,...) instead of creating a new player for each file... Ciao, -- FA ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] jackdbus log controls?
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-...@lists.linuxaudio.org > https://lists.linuxaudio.org/listinfo/linux-audio-dev signature.asc Description: This is a digitally signed message part ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] jackdbus log controls?
On 2019-11-24 15:51:04 (-0700), Ethan Funk wrote: > How do I get control over jackdbus logging? I currently have an > gigantic log file it is creating at ~/.log/jack/jackdbus.log from my > testing. You can look into logrotate [1] to auto-cleanup and rotate the log (check `man 5 logrotate.conf` and `man 8 logrotate`). You can run this on a systemd timer or cron job. > It's huge because my application make extensive use of jacks inter- > process audio routing as a radio station automation system. My > application is endlessly forking new audio player processes that > connect back to a core mixer via jack, play when needed, then > disconnect when finished. So the above log file is crammed full of > jack port connect and disconnect notices. How do I make it stop? I'm uncertain (because I run jackd in a systemd user unit [2] and haven't used jackdbus in a long time), but there is a ticket around the logging facilities [3]. Best, David [1] https://github.com/logrotate/logrotate [2] https://github.com/jackaudio/jack2/tree/develop/systemd [3] https://github.com/jackaudio/jack2/issues/402 -- https://sleepmap.de signature.asc Description: PGP signature ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] jackdbus log controls?
On Sun, 24 Nov 2019, Ethan Funk wrote: I am almost a week into testing my jack-audio application with no crashes of jackd or my application. Bug abound (in my code), but that is the point of testing. 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 file it 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 Ovens www.ovenwerks.net ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
[LAD] jackdbus log controls?
I am almost a week into testing my jack-audio application with no crashes of jackd or my application. Bug abound (in my code), but that is the point of testing. 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 file it is creating at ~/.log/jack/jackdbus.log from my testing. It's huge because my application make extensive use of jacks inter- process audio routing as a radio station automation system. My application is endlessly forking new audio player processes that connect back to a core mixer via jack, play when needed, then disconnect when finished. So the above log file is crammed full of jack port connect and disconnect notices. How do I make it stop? There is no man page available for jackdbus, and "ps" indicates that it was simply run as "/usr/bin/jackdbus auto." With some further poking around I found that ubuntu-syudio-control is running something called autojack, which seems to run jackdbus, and autojack does have a man page, but not much help. As a side note, the Patchage interconnection GUI does seem to cause jackd to crash after about two days of running. I have not troubleshot that any further, but I do know that without Patchage running, jackd has been running with my program for 5 days. There may be something worth investigating, but I haven't had time. Thanks, Ethan... signature.asc Description: This is a digitally signed message part ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
