argus instability

[carter at qosient.com]

When a debug statement works, its usually a stack problem, but this looks like you're just slowing argus down.  This helps a great deal!!!

Carter


Carter Bullard
QoSient LLC
150 E. 57th Street Suite 12D
New York, New York 10022
+1 212 588-9133 Phone
+1 212 588-9134 Fax

-----Original Message-----
From: Peter Van Epp <vanepp at sfu.ca>

Date: Thu, 5 Jul 2007 10:56:24 
To:argus-info at lists.andrew.cmu.edu
Subject: [ARGUS] argus instability


	A data point. Adding a debug statement to argus/Argus_client.c seems
to have made argus stable here. It hasn't died in the last 24 hours after 
this statement was added (I'm about to remove it again to see if it really
is having an effect :-)):

line 1223:

            if (((retn = write (asock->fd, asock->buf, cnt)) < cnt)) {
               if (retn < 0) {
                  if ((errno == EAGAIN) || (errno == EINTR) ||
                     ((errno == EPIPE) && !(asock->status & ARGUS_WAS_FUNCTIONAL)))
                     retn = 0;
                  else {
#ifdef ARGUSDEBUG
            ArgusDebug (2, "ArgusWriteSocket: errno %d\n", errno);
#endif
                     return (retn);
                  }
               }
            } else


#ifdef ARGUSDEBUG
            ArgusDebug (2, "ArgusWriteSocket: errno %d\n", errno);
#endif

was added above as well as a bunch of the debug levels set to 2 in this 
same routine. 

Peter Van Epp / Operations and Technical Support 
Simon Fraser University, Burnaby, B.C. Canada