SIGURG is the urgent data indicator. It isnt reliable at the TCP protocol level
because multiple queued urgent data markers can be in flow together and there
is only one urgent data pointer.
Nobody appears to have filed a bug about it, so I would assume there isn't one.
Ask your Database vendor to actually report this if they have a bug and
include some kind of small demo code example if possible.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/