Re: Semaphore / Synchronizing write operations

"vsaavedra" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
With your help, I managed to implement the lock mechanism :-D



But, after some tests, I realize I need to improve this mechanism.



I'm thinking in the following approach :



Instead of using a spinlock scalar, this object will be a leaf in a table.
But to do this, I will have to modify the handler for that table with the
following algorithm:



 mainTable_handler(netsnmp_mib_handler *handler, ..)

{

            If(column is the spinlockObject)

            {

case MODE_SET_RESERVE1:

        if ( spinLockValue  != table.spinlockLeaf)

            netsnmp_set_request_error(reqinfo, requests,
SNMP_ERR_WRONGVALUE);

        break;



    case MODE_SET_ACTION:

        Table.spinlockLeaf ++;

}

}



Does this make any sense ? :-D



----- Original Message ----- 
From: "Dave Shield" <[email protected]>
To: "vsaavedra" <[email protected]>
Cc: <[email protected]>
Sent: Tuesday, October 23, 2007 3:48 PM
Subject: Re: Semaphore / Synchronizing write operations


> On 23/10/2007, vsaavedra <[email protected]> wrote:
> > When using a spinlock aproach, should I do :
> >
> > snmpset -v 2c -c public localhost SpinLockObject i 0 MyLeaf i 1
>
> No.
>
> First of all, the spinLockObject is a scalar object, so you need
> to give the OID of the (sole) instance - i.e.  spinLockObject.0
>
> Secondly, you need to give the correct spin-lock value - not 0.
> Otherwise the SET will fail. That's the whole point of a spin-lock.
>
> I suggest you re-read the description of the TestAndIncr syntax
> (in the SNMPv2-TC MIB)
>
> Dave
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> 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
>


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.