[15:19] Eickmeyer: thats weird, maybe not, it says may 14. I was looking at my jack log file and it says: setting parameter 'drivers':'firewire':'rate' to [15:26] O_O [15:26] Interesting. [15:27] even more interesting is why do I even have such old information [15:28] and can I set jackdbus to not log so much and can I get log rollover deal with files in ~/.log? [15:30] I think we should have autojack on start rename the jack log file *.1 (and if there is a *.1 call it *.2 and if there is a *.2 remove it) [15:31] stupid other question but have you considered tweaking logrotate? [15:32] to rotate daily or such? [15:32] ah wait, ~/.log [15:32] nevermind [15:32] * teward001 misread [15:32] :) [15:32] ya jack is user sapce [15:35] ERR:NEEDMORECOFFEE [15:35] I:OBTAININGCOFFEE [15:35] E:COFFEENOTAVAILABLE … [Kernel Panic] [15:35] anyways. [15:35] Eickmeyer: nope it is still happening. Setting firewire and dummy backend parameters at every startup [15:36] it is no harming anything as it still starts up ok, but it is not right. Anyway that is not the user in #ubuntustudio problem. [15:38] Agreed, but if we found a bug, it makes sense to fix it before final freeze for sure. [15:38] As for wonko's issue, that's definitely a sleep with jack running issue. Jack doesn't like to sleep. [15:39] Back later, gotta get kid to school [15:39] * OvenWerks just found out his son is too sick for school [15:57] I think we can actually use logrotate. It can be set to daily but run each time the daemon is started. If it is started more than once a day, it will still only work once and if the session is left open (as I do) it may be a while before it gets rotated. I could even have it run at each jack start. [15:58] posted that in the wrong place first time... [16:09] Not a bad idea.