why does uint64_t arrive with reverse order in notification?
Alexander Bubnov <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
Hello, all!
subj. is it a bug?
const oid runtime_task_oid[] = {...};
const size_t runtime_task_oid_length = OID_LENGTH(runtime_task_oid);
//runtime_task_id = (runtime_task_id<<32)|(runtime_task_id>>32); if I
uncomment this line I can receive notification in exceted order
const u_char * runtime_task_id_value = reinterpret_cast(&runtime_task_id);
const size_t runtime_task_id_value_length = sizeof(runtime_task_id);
snmp_varlist_add_variable( ¬ification_vars, persistent_task_oid,
persistent_task_oid_length, ASN_COUNTER64, (const u_char *)
persistent_task_id_value, persistent_task_id_value_length );
send_v2trap(notification_vars); snmp_free_varbind(notification_vars);
Thanks in advance!
--
/BR, Alexander
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
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