>    RETURN VALUE
>       On success, select and pselect return the number  of  descriptors 
>       contained in the descriptor sets, which may be zero if the timeout
>       expires before anything interesting happens.

I do have the man pages installed, it just didn't dawn on me to look 
there.
So then the return value is then pretty useless if I wanted to make some
sense of what is causing the select to return.  That is, it's just a count
and not a value that would describe that select returned because of a file
descriptor write, a socket or pipe write, a msg queue receive, etc.

So right now if we get a non-zero return (or between 1 and n) then we try
to process the information.  This effectively calls 
agent_check_and_process
everytime.  And only when it's the incoming Get packet do we go and do the
dirty work to process it.  But I'm wondering if it might be useful to 
figure out in my code whether it's really the incoming Get request before
calling agent_check_and_process (so as to not cause as much undo "churn").

Or maybe it's correct for agent_check_and_process to figure this out and I
shouldn't fix what's not broke.

Thanks,

Carlos



-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Net-snmp-users mailing list
[EMAIL PROTECTED]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to