iSeghal queue overflow

[Marco Filho via Tech-talk <tech-talk at aps.anl.gov>]

Hello all

I'm using iSegHal epics module to control an equipment and I keep getting lots of queue overflows but I can't find where they are coming from:

(...)

0.6.33.EventMask: Warning: iseg Client Mgt queue overflow.
0.6.33.DelayedTripAction: Warning: iseg Client Mgt queue overflow.
0.6.33.ExternalInhibitAction: Warning: iseg Client Mgt queue overflow.
0.6.34.EventMask: Warning: iseg Client Mgt queue overflow.
0.6.34.DelayedTripAction: Warning: iseg Client Mgt queue overflow.
0.6.34.ExternalInhibitAction: Warning: iseg Client Mgt queue overflow.
(...)

etc...

The IOC operation seems to work, but this is flooding my logs. I tried:

devIsegHalSetOpt("LogLevel", "0")

But to no avail. Also, I noticed that in the source code:

    if( strcmp( args[1].sval, "LogLevel" ) == 0 ) {
      if( iseg_setItem( args[0].sval, "LogLevel", args[2].sval ) != ISEG_OK ) {
        fprintf( stderr, "\033[31;1mCould not change LogLevel to '%s'\033[0m\n", args[2].sval );
        return;
      }
    }

However, if I try to set the logLevel to a garbage value, nothing is printed to my stderr:

2098138 > devIsegHalSetOpt("LogLevel", "NoMoreLogsPlease")
2098138 >

Also, I tried grepping "queue overflow" in both the devISegHal and the iseghal source code but found nothing that made sense to me. Is this message coming directly from epics base? Is there any way to allocate a bigger queue (what is this queue?) to avoid overflow?

Thanks in advance for any help,

Marco.