Well, lo and behold now that I've built a script including one that comments on when the shutdown was initiated, I cannot reproduce the problem, yet I do know it has happened in the past. Perhaps because this is a script and not an individual command? Or, it could be that when the CPU is getting hogged by other things and I shutdown qjackctl it somehow does not give enough time to propagate (this is on an Atom netbook). Or, there is always the safe bet that I am hallucinating and we leave it at that :-) I will keep the script going to see what happens and will let you know. Many thanks for all your help. Best wishes, Ico > -----Original Message----- > From: Rui Nuno Capela [mailto:rncbc@xxxxxxxxx] > Sent: Tuesday, October 20, 2009 7:28 PM > To: Ivica Ico Bukvic > Cc: linux-audio-user@xxxxxxxxxxxxxxxxxxxx > Subject: Re: bug in qjackctl 0.3.5 > > Ivica Ico Bukvic wrote: > >> #/bin/bash > >> cpufreq-set -g ondemand > qjackctl_cpufreq.log 2>&1 > > > > Unfortunately this particular app generates no output whatsoever so > logging > > it does absolutely nothing. Its help file also suggests there is no way to > > produce a verbose version either. > > > > Any other ideas? > > > > Ico > > let the script be more elaborate: > > #!/bin/bash > cpufreq-set -g ondemand > rc=$? > echo "`date` rc=$rc" >> qjackctl_cpufreq.log > > -- > rncbc aka Rui Nuno Capela > rncbc@xxxxxxxxx _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
