Re: IRC chat to help our new guard get on board?
Bart, Thank you for your interest. Please let us know when you're free; we will schedule the meeting based on what works best for the net-snmp devs who would like to join us. Thanks, Keith On Tue, Apr 3, 2018 at 7:11 PM, Bart Van Assche wrote: > On 04/03/18 17:54, Eric S. Raymond wrote: >> >> ICEI has a #newguard channel on freenode where its "new guard" - >> programmers who want to get involved in infrastructure work - hang >> out. >> >> Some of them are interested in contributing to net-snmp. Joining Ian >> on the bug triage would be an obvious way to on-board them, but that >> will work better if they have more sense of the scope and direction of >> the project and feel like they know its key people. >> >> We'd like to set up a time for a short IRC conference for them to get >> to know your project's senior devs and vice-versa. Ian and Keith and I >> will be there, of course. We can talk about what needs to be done and >> recruit you some more help. >> >> We'd like to especially invite your project owner and release manager >> and tech lead (understanding that those might be the same person) but >> any net-snmp dev would be welcome and the more the better >> >> If you're willing to attend, please respond with your name, your >> project role, and some indication of when you could be free for a >> 45-minute IRC chat within the next ten days. > > > Hello Eric, > > I'm willing to attend but whether I will be able to attend will depend on > when the IRC-chat will be held. I'm one of the Net-SNMP developers. Most > work on the Windows ports (MSVC, Cygwin, MinGW) is done by me but as one can > see in the git tree I make contributions all over the Net-SNMP tree. > > Bart. > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Net-snmp-coders mailing list > Net-snmp-coders@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: IRC chat to help our new guard get on board?
On 04/03/18 17:54, Eric S. Raymond wrote: ICEI has a #newguard channel on freenode where its "new guard" - programmers who want to get involved in infrastructure work - hang out. Some of them are interested in contributing to net-snmp. Joining Ian on the bug triage would be an obvious way to on-board them, but that will work better if they have more sense of the scope and direction of the project and feel like they know its key people. We'd like to set up a time for a short IRC conference for them to get to know your project's senior devs and vice-versa. Ian and Keith and I will be there, of course. We can talk about what needs to be done and recruit you some more help. We'd like to especially invite your project owner and release manager and tech lead (understanding that those might be the same person) but any net-snmp dev would be welcome and the more the better If you're willing to attend, please respond with your name, your project role, and some indication of when you could be free for a 45-minute IRC chat within the next ten days. Hello Eric, I'm willing to attend but whether I will be able to attend will depend on when the IRC-chat will be held. I'm one of the Net-SNMP developers. Most work on the Windows ports (MSVC, Cygwin, MinGW) is done by me but as one can see in the git tree I make contributions all over the Net-SNMP tree. Bart. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
IRC chat to help our new guard get on board?
ICEI has a #newguard channel on freenode where its "new guard" - programmers who want to get involved in infrastructure work - hang out. Some of them are interested in contributing to net-snmp. Joining Ian on the bug triage would be an obvious way to on-board them, but that will work better if they have more sense of the scope and direction of the project and feel like they know its key people. We'd like to set up a time for a short IRC conference for them to get to know your project's senior devs and vice-versa. Ian and Keith and I will be there, of course. We can talk about what needs to be done and recruit you some more help. We'd like to especially invite your project owner and release manager and tech lead (understanding that those might be the same person) but any net-snmp dev would be welcome and the more the better If you're willing to attend, please respond with your name, your project role, and some indication of when you could be free for a 45-minute IRC chat within the next ten days. -- http://www.catb.org/~esr/";>Eric S. Raymond It would be thought a hard government that should tax its people one tenth part. -- Benjamin Franklin -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Multiple rwuser directives for the same user
Hello everyone, I'm facing problem with multiple rwuser directives for the same user in my config file. Just the first one is applied and the second one is ignored. I saw something like this in the docs: "It is not appropriate to specify both rouser and rwuser directives referring to the same SNMPv3 user". But that's not my case. Can someone please give me more info about this behaviour? -- Best regards, J.G. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: sysUptime uses gettimeofday
Thank you Stuart Henderson. On Tue, Apr 3, 2018 at 3:51 PM, Stuart Henderson wrote: > On 2018/04/03 15:25, Pushpa Thimmaiah wrote: > > Thank you Magnus Fromreide, Anders Wallin and Stuart Henderson for the > reply. > > > > Stuart Henderson, > > > > I am using net-snmp.5.7.1. Object sysUpTime uses API > netsnmp_get_agent_uptime() and they > > inturn uses gettimeofday(). > > If time on device changes after snmpd starts then sysUpTime value is > confusing. > > Scenario: > > 1. Linux device time is 'Mon Aug 28 21:01:29 UTC 2017' > > 2. start snmpd > > 3.Now sysUptime = 4 seconds > > 4. Set linux device time 'Mon Mar 26 05:53:07 UTC 2018' > > 5. sysUptime = 209 days <-- This is not correct in this scenario. > > You should update. The latest 5.7 release is 5.7.3 which is already 3 > years old; > the change to CLOCK_MONOTONIC was done in 5.7.2. > > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: default interface to send traps
Thank you Bill Fenner. On Thu, Mar 29, 2018 at 5:01 PM, Bill Fenner wrote: > On Thu, Mar 29, 2018 at 5:57 AM, Pushpa Thimmaiah < > pushpa.thimma...@gmail.com> wrote: > >> Query 1. Which interface does 'snmptrap'/snmpd use to send traps out? >> > > It will use the kernel's routing table. > > >> Query 2. Suppose, eth1 firewall blocks 'snmp' packets then >> Does 'snmpd/snmptrap' use eth2 port to traps out >> > > No. > > Bill > > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: sysUptime uses gettimeofday
Thank you Magnus Fromreide, Anders Wallin and Stuart Henderson for the reply. Stuart Henderson, I am using net-snmp.5.7.1. Object sysUpTime uses API netsnmp_get_agent_uptime() and they inturn uses gettimeofday(). If time on device changes after snmpd starts then sysUpTime value is confusing. Scenario: 1. Linux device time is 'Mon Aug 28 21:01:29 UTC 2017' 2. start snmpd 3.Now sysUptime = 4 seconds 4. Set linux device time 'Mon Mar 26 05:53:07 UTC 2018' 5. sysUptime = 209 days <-- This is not correct in this scenario. Thank you, Pushpa.T On Fri, Mar 30, 2018 at 2:01 PM, Stuart Henderson wrote: > In gmane.network.net-snmp.devel, you wrote: > > I believed that sysUpTime is counter that increments every seconds. But > In > > net-snmp code , > > sysUpTime being calculated as difference between 'snmpd-starttime' and > > 'current time' . > > > > I would like to know reason for sysUpTime been calculated as difference > in > > time instead of incremental-counter. > > Is there any constraints ? > > Which version are you looking at? net-snmp has been using clock_gettime > with (incremental) CLOCK_MONOTONIC for sysUptime for about 6 years. > > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
