I just did some cleaning on the computer and found this file:
~/.log/jack/jackdbus.log
It was 860 MB long, with events logged since as recently as March 1st 2016.
I recommend keeping an eye on it. I don't know about you, but I don't think I have any use for jackdbus log data older than a couple of days, and I was really glad to have that much disk space back. Like finding money at the bottom of a drawer.
TIP: reclaim lots of disk space from jackdbus.log
Moderators: MattKingUSA, khz
Re: TIP: reclaim lots of disk space from jackdbus.log
Thanks for the tip. I just checked and it is "only" 27 MB here.
Cheers! Pablo
Cheers! Pablo
Re: TIP: reclaim lots of disk space from jackdbus.log
Just happened again. This time, 1.6 GB!
If you had never seen this thread, check your ~/.log/jack/jackdbus.log file.
If you had never seen this thread, check your ~/.log/jack/jackdbus.log file.
- English Guy
- Established Member
- Posts: 525
- Joined: Wed Oct 17, 2012 7:28 pm
- Location: England
- Has thanked: 8 times
- Been thanked: 7 times
Re: TIP: reclaim lots of disk space from jackdbus.log
If it is an issue perhaps a script and cron job are in order. Very useful to know when using on a Raspberry Pi with an 8GB sd card.
Re: TIP: reclaim lots of disk space from jackdbus.log
Interesting. Thank you for the info.falkTX wrote:If up have kxstudio-default-settings package installed this file should be automatically compressed every 10 days.
Is that log really useful for anything?
Re: TIP: reclaim lots of disk space from jackdbus.log
I just found another disk waster: /boot/run.log. It had amounted to 1.1 GB when I found it.
Clearly, many other apps write to that log, but I found this exact line repeated many tens of thousands of times:
JackClientSocket::Read time out
Tens of thousands, possibly hundreds of thousands. I got tired of scrolling after about a minute, then deleted it, should have run sed and wc to get the exact count.
To whomever this may concern.
Clearly, many other apps write to that log, but I found this exact line repeated many tens of thousands of times:
JackClientSocket::Read time out
Tens of thousands, possibly hundreds of thousands. I got tired of scrolling after about a minute, then deleted it, should have run sed and wc to get the exact count.
To whomever this may concern.