Re: [nas] many 'doSetup: elementRate == 0! Forcing to 5000'

[Jon Trulson <jon@xxxxxxxxxxx>]

On Mon, 21 Jul 2008, hugo vanwoerkom wrote:

> Hi,
>
> I get 1000's of
>
> doSetup: elementRate == 0! Forcing to 5000
>
> in syslog. What is the best way to get rid of those?

  How about this patch (attached).  Technically the element rate should
  always be specified, but that doesn't always happen as you an see :)

  This patch prevents this diagnostic from being logged unless the
  debug level is above 10.

> Thanks!
>
> Hugo Vanwoerkom

--
Happy cheese in fear                 | Jon Trulson
against oppressor, rebel!            | mailto:jon@xxxxxxxxxxx
Brocolli, hostage.       -Unknown    | #include <std/disclaimer.h>

Index: server/dia/auprocess.c
===================================================================
--- server/dia/auprocess.c	(revision 273)
+++ server/dia/auprocess.c	(working copy)
@@ -30,6 +30,8 @@
 #include <audio/Aproto.h>
 #include "au.h"
 
+#include "nasconf.h"
+
 AuInt32 auMinibufSamples;
 AuUint32 auPhysicalOutputBuffersSize;
 AuUint8 *auPhysicalOutputBuffers;
@@ -1100,8 +1102,9 @@
 
     /* sanity - 6/20/2004, for bug report by Tobias Diedrich */
     if (!elementRate) {
-        osLogMsg("doSetup: elementRate == 0! Forcing to %d\n",
-                 auSetup.minSampleRate);
+        if (NasConfig.DoDebug > 10)
+            osLogMsg("doSetup: elementRate == 0! Forcing to %d\n",
+                     auSetup.minSampleRate);
         elementRate = auSetup.minSampleRate;
     }