Net-SNMP Wiki - User contributions [en]

Git For Developers

2013-01-08T08:42:10Z

Dts12: Update (anonymous) URL to use the new Allura-style repository (and ensure a careless cut-n-paste won't try to retrieve 'MODULE')

[[Git]] is a distributed version control system. This page provides information for developers on how we manage our sources within git.

== Public Repo ==
This page is mean for the Net-SNMP development team. If you're looking for the page on the read-only git repo available to the general public, see the [[Git]] page.

== Setup ==

git clone ssh://USERNAME@git.code.sf.net/p/net-snmp/code

(This will retrieve the source code for the project. To obtain the content of the Net-SNMP website, replace ''code'' with ''htdocs'')

A variation of this is to use ssh only to push changes and the git protocol to pull, this is achived by

git clone git://git.code.sf.net/p/net-snmp/code
cd code
git config remote.origin.pushurl ssh://USERNAME@git.code.sf.net/p/net-snmp/code

Make sure your email address and name are correct:

git config user.email "''YOURSFACCOUNTNAME''@users.sourceforge.net"
git config user.name "''YOUR NAME''"

== Git workflows ==

The first link below should be read before any code is checked in. Specifically, it describes the one important aspect: '''always commit to the lowest branch you want the patch to apply to!'''

* First and foremost, read Net-SNMP's [[Git Workflow]]
* Then, consider using the [[Git Branch Management]] macros for performing the routine tasks (branch merging, etc).
* [http://www.kernel.org/pub/software/scm/git/docs/gitworkflows.html The gitworkflows manual page] is similar to ours
* [http://nvie.com/img/2009/12/Screen-shot-2009-12-24-at-11.32.03.png A good diagram] showing another similar workflow pattern.

=== Making changes ===

This is where you type ''vi'' or ''emacs'' or if you're a real developer who likes to get dirty ''perl -i -p -e ...''

=== Checking out the right branch ===

git maintains all the code in a single directory, and lets you switch between the branches in the same directory. This is very very different than SVN and other repository systems, but most people find once they let go of the idea that they need separate directories, they're happier in the long run.

The branch may not exist yet in your local repository (run ''git branch -a'' to list all the branches known, including the remote ones). To start, simply check it out:

# '''git checkout V5-4-patches'''
Branch V5-5-patches set up to track remote branch V5-5-patches from origin.
Switched to a new branch 'V5-5-patches'

(and now 'git branch' without the '-a' will list it as a known local branch).

=== Moving changes to a different branch ===

If you have changes in the local repository already and want to apply them (or test them) against a different branch, the easiest way to do this is with ''stash'' and ''pop'':

# '''git checkout V5-6-patches'''
error: Your local changes to the following files would be overwritten by checkout:
NEWS
Please, commit your changes or stash them before you can switch branches.
Aborting

# '''git stash'''
Saved working directory and index state WIP on V5-5-patches: 6a5e5a6 Merge branch 'V5-4-patches' into V5-5-patches
HEAD is now at 6a5e5a6 Merge branch 'V5-4-patches' into V5-5-patches

# '''git checkout V5-6-patches'''
Branch V5-6-patches set up to track remote branch V5-6-patches from origin.
Switched to a new branch 'V5-6-patches'

# '''git stash pop'''
Auto-merging NEWS
# On branch V5-6-patches
# Changes not staged for commit:
# (use "git add <file>..." to update what will be committed)
# (use "git checkout -- <file>..." to discard changes in working directory)
#
# modified: NEWS
#
no changes added to commit (use "git add" and/or "git commit -a")
Dropped refs/stash@{0} (102700302cd0a9db42b1669105291bb92fe807e9)

=== Committing the changes ===

# git commit -m "commit message" ''FILES''

Or if you want to commit everything in a directory and down, use a directory name instead of ''FILES''.

Or if you want to commit everything anywhere in the repo, use the ''-a'' switch.

'''NOTE:''' this only commits them to your local copy of the repository. This is different than [[SVN]], if you're more familiar with SVN. Next you need to ''push'' them to the master repository:

=== Pulling the latest changes from the upstream ===

Whether or not you've modified files locally and checked in the changes to your local repository, you'll need to occasionally pull down any changes that others have made upstream. You do this with a ''pull''. The --rebase option means rather than treat your development as a parallel set, try and apply your resulting patches to the end of the pulled branch instead of merging them. This tends to keep a cleaner history tree.

# git pull --rebase origin master

Assuming you followed the instructions above, and didn't cloning from somewhere else first, you should be able to shorten this to:

# git pull --rebase

This will merge any changes you've made with any that others have made. If something goes wrong, git will complain about conflicts and you'll need to resolve those either manually or using ''git mergetool''. That's a longer subject for another lesson: [[Git Merging]].

You may also wish to pull all the remote branches:

# git pull --all

=== Reviewing local commits ===

The most effective way to use git is to commit changes to the local tree as multiple small changes. That makes it easy to edit or revert any local changes if necessary. Once the local changes have been tested and before pushing these upstream, review the local changes and rearrange these if necessary. Try to make sure that any contributed change at least compiles such that the tree remains bisectable. One way to edit local commits is via the git rebase command. That command does not only allow to change the description of each commit, to change the order of commits, to squash multiple commits together but also to leave out some commits. Of course, if any changes have been made these have to be retested. The rebase command can be invoked as follows when working on the master branch:

# git rebase --interactive origin/master

=== Pushing the changes upstream ===

Once you're sure your commits are safe themselves and you've updated your repo with the latest upstream you can push your changes upstream to the master repository on sourceforge:

# git push origin master

Assuming you followed the instructions above, and didn't cloning from somewhere else first, you should be able to shorten this to:

# git push

And you're done!

=== Notes on the htdocs repository ===

The ''htdocs'' module, which contains the Net-SNMP website, is only synchronized from the git repository once an hour. It may take up to an hour before the changes take effect on the website.

== Creating tags and branches ==

=== Tagging ===

Tags are simply a symbolic way of remembering "a point in time" that is easier than the sha1 hash that is more frequently seen.

git tag my-really-super-feature-works

for example will create the above tag.

'''XXX: discuss annotated/signed/etc tags'''

=== Pushing tags ===

By default, ''git push'' doesn't push tags. IE, it *only* pushes code. If you've created a tag and you want it pushed upstream, you'll need to push it manually:

git push origin ''TAGNAME''

Or you can push '''all your tags''':

git push --tags

Note: Please don't push personal tags... Use the individual push instead if you're creating helpful personal tags.

[[Category:Git]]

Git

2013-01-08T08:37:13Z

Dts12: Use the correct URL for the new (allura) repository in the anonymous retrieval instructions

Git is a version control system (VCS) that is based on a distributed architecture. In June 2011, the Net-SNMP project switched from [[SVN]] to '''Git'''. In December 2012, the project moved to the new 'Allura' SourceForge framework, which also affected the URLs used to retrieve the code. Please ensure that you use the repositories shown below - using anything else may result in obtaining an old version of the project code.

If you're a developer, you might checkout out the [[Git For Developers]] page.

== Checking out the Net-SNMP Git Tree ==

Check it out anonymously (read-only access):
git clone git://git.code.sf.net/p/net-snmp/code

Checking it out if you're a developer:
git clone ssh://''USERNAME''@git.code.sf.net/p/net-snmp/code

This will retrieve the source code for the project.
(To obtain the content of the Net-SNMP website, replace ''code'' with ''htdocs'')

== Learning Git ==

If you're starting out learning Git, here are some useful resources:

* If you're familiar with SVN, read the [http://git.or.cz/course/svn.html Git - SVN Crash Course]
* The git manual pages. In particular:
** [http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html the Git tutorial]
** [http://www.kernel.org/pub/software/scm/git/docs/gittutorial-2.html the Git tutorial, part 2]
** [http://www.kernel.org/pub/software/scm/git/docs/git.html The main git manual page]

== See Also ==

Also, check out the contents of the Git category which lists even more resources:

[[Category:Git]]

Git

2013-01-08T08:33:38Z

Dts12: Update (anonymous) URL to use the new Allura-style repository (and ensure a careless cut-n-paste won't try to retrieve 'MODULE')

Git is a version control system (VCS) that is based on a distributed architecture. In June 2011, the Net-SNMP project switched from [[SVN]] to '''Git'''. In December 2012, the project moved to the new 'Allura' SourceForge framework, which also affected the URLs used to retrieve the code. Please ensure that you use the repositories shown below - using anything else may result in obtaining an old version of the project code.

If you're a developer, you might checkout out the [[Git For Developers]] page.

== Checking out the Net-SNMP Git Tree ==

Check it out anonymously (read-only access):
git clone git://net-snmp.git.sourceforge.net/gitroot/net-snmp/code

Checking it out if you're a developer:
git clone ssh://''USERNAME''@git.code.sf.net/p/net-snmp/code

This will retrieve the source code for the project.
(To obtain the content of the Net-SNMP website, replace ''code'' with ''htdocs'')

== Learning Git ==

If you're starting out learning Git, here are some useful resources:

* If you're familiar with SVN, read the [http://git.or.cz/course/svn.html Git - SVN Crash Course]
* The git manual pages. In particular:
** [http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html the Git tutorial]
** [http://www.kernel.org/pub/software/scm/git/docs/gittutorial-2.html the Git tutorial, part 2]
** [http://www.kernel.org/pub/software/scm/git/docs/git.html The main git manual page]

== See Also ==

Also, check out the contents of the Git category which lists even more resources:

[[Category:Git]]

Notes20130107

2013-01-07T20:30:47Z

Dts12: Testing editing

{{meetingtime|time=20|year=2013|month=01|day=07|nextyear=2013|nextmonth=02|nextday=04|prevyear=2012|prevmonth=10|prevday=22}}

* Next Date
** '''Feb 4'''
* Releases
** up now: from 20120723: concentrate on patches/bugs instead of a release
* Administrative
** wiki issues
*** '''Wes just upgraded to 1.20.2 and it seems to be working properly now'''
** PERSIST: Switch to [http://sourceforge.net/p/allura/wiki/Features/ Allura]?
*** '''has been switched to'''
*** '''git mailings seem to have broken; Wes will look into re-enabling the hook'''
*** '''dts12 wishes for:'''
**** '''better sorting and better filtering'''
**** world peace and harmony
**** three more days in the week
** Adding a "this is an old release" header to the README and other files for older branches?
*** lots of abstains and one no: kill the idea
* Technical
** PERSIST: Time kill off redundant modules?
*** '''general feeling of 'yes' prevailed; need a list of what to consider though''''
*** [[obsolete agent modules to remove]]
* Roundtable
** me: hopefully bugs

Notes20120723

2012-07-23T18:55:42Z

Dts12:

Administrative Meetings

2012-06-18T16:48:17Z

Dts12: Meeting put back a week

The Net-SNMP administrative staff holds meetings on IRC on a regular basis to discuss project issues, goals, etc. The meetings are run on the #net-snmp-admin channel. Anyone can join and participate. To add agenda items, simply add them to the list in the upcoming meetings pages. If you feel the minutes of past meetings are in error, please edit them as appropriate.

== Upcoming Meetings ==

* [[Notes20120618 | 2012-06-18]]

== Notes From Previous Meetings ==

* [[Notes20120507 | 2012-05-07]]
* [[Notes20120402 | 2012-04-02]]
* [[Notes20120227 | 2012-02-27]]
* [[Notes20120116 | 2012-01-16]]
* [[Notes20111219 | 2011-12-19]]
* [[Notes20111024 | 2011-10-24]]
* [[Notes20110926 | 2011-09-26]]
* [[Notes20110808 | 2011-08-08]]
* [[Notes20110620 | 2011-06-20]]
* [[Notes20110523 | 2011-05-23]]
* [[Notes20110425 | 2011-04-25]]
* [[Notes20110321 | 2011-03-21]]
* [[Notes20110221 | 2011-02-21]]
* [[Notes20110131 | 2011-01-31]]
* [[Notes20110103 | 2011-01-03]]
* [[Notes20101129 | 2010-11-29]]
* [[Notes20101011 | 2010-10-11]]
* [[Notes20100920 | 2010-09-20]]
* [[Notes20100809 | 2010-08-09]]
* [[Notes20100607 | 2010-06-07]]
* [[Notes20100517 | 2010-05-17]]
* [[Notes20100419 | 2010-04-19]]
* [[Notes20100315 | 2010-03-15]]
* [[Notes20100222 | 2010-02-22]]
* [[Notes20100111 | 2010-01-11]]
* [[Notes20091214 | 2009-12-14]]
* [[Notes20091116 | 2009-11-16]]
* [[Notes20091012 | 2009-10-12]]
* [[Notes20090914 | 2009-09-14]]
* [[Notes20090810 | 2009-08-10]]
* [[Notes20090720 | 2009-07-20]]
* [[Notes20090615 | 2009-06-15]]
* [[Notes20090518 | 2009-05-18]]
* [[Notes20090406 | 2009-04-06]]
* [[Notes20090302 | 2009-03-02]]
* [[Notes20090202 | 2009-02-02]]
* [[Notes20090105 | 2009-01-05]]
* [[Notes20081110 | 2008-11-10]]
* [[Notes20081006 | 2008-10-06]]
* [[Notes20080915 | 2008-09-15]]
* [[Notes20080811 | 2008-08-11]]
* [[Notes20080707 | 2008-07-07]]
* [[Notes20080602 | 2008-06-02]]
* [[Notes20080509 | 2008-05-09]]
* [[Notes20080331 | 2008-03-31]]
* [[Notes20080211 | 2008-02-11]]
* [[Notes20080115 | 2008-01-15]]
* [[Notes20071211 | 2007-12-11]]
* [[Notes20071114 | 2007-11-14]]
* [[Notes20071009 | 2007-10-09]]
* [[Notes20070919 | 2007-09-19]]
* [[Notes20070823 | 2007-08-23]]
* [[Notes20070719 | 2007-07-19]]
* [[Notes20070705 | 2007-07-05]]
* [[Notes20070601 | 2007-06-01]]
* [[Notes20070511 | 2007-05-11]]
* [[Notes20070406 | 2007-04-06]]
* [[notes20070302 | 2007-03-02]]
* [[notes20070209 | 2007-02-09]]
* [[notes20061222 | 2006-12-22]]
* [[notes20061122 | 2006-11-22]]
* [[notes20061103 | 2006-11-03]]
* [[notes20060928 | 2006-09-28]]
* [[notes20060908 | 2006-09-08]]
* [[notes20060804 | 2006-08-04]]

== Future Topics ==

These items are likely topics for future discussions when time permits:

* The Great Rename (aka "svn move")
** consistent structure
** path names shorter than 100 chars to minimize tar problems
* [[Google SoC]] 2009

== Bug Bash ==

For a while, there were also separate [[BugBash]] meetings on IRC.
However these have fallen into disuse, and have not happened recently.

[[Category:Admin]]

Notes20120618

2012-06-18T16:47:44Z

Dts12: moved Notes20120611 to Notes20120618: Meeting put back a week

Notes20120611

2012-06-18T16:47:44Z

Dts12: moved Notes20120611 to Notes20120618: Meeting put back a week

#REDIRECT [[Notes20120618]]

Notes20120507

2012-06-18T16:47:11Z

Dts12: Reverted edits by Dts12 (talk) to last revision by Wes

{{meetingtime|time=19|year=2012|month=05|day=07|nextyear=2012|nextmonth=06|nextday=11|prevyear=2012|prevmonth=04|prevday=02}}

* Next Date
* Releases
** 5.5/5.6 -- dts12
*** rc1 being done as we speak
** 5.7 after that -- Wes
*** needs to start
* Administrative
** Git
*** merging resolving of configure, NEWS, README, ...
*** '''we need a update-these script that protects them'''
*** '''dts12 finished making the makerelease modifications to make it do the right merge -s ours'''
**** '''hardaker will review as a second pair of eyes'''
** Wiki Front Page
* Technical
** Coverity scan results
* Roundtable
** hardaker needs to start a 5.7 branch release
** dts12 needs to finish 5.5/6.2
** magfr needs to finish the transport cleanup
** nba needs to incorporate the BSD patches and push them

Notes20120507

2012-06-18T16:46:29Z

Dts12:

{{meetingtime|time=19|year=2012|month=05|day=07|nextyear=2012|nextmonth=06|nextday=18|prevyear=2012|prevmonth=04|prevday=02}}

* Next Date
* Releases
** 5.5/5.6 -- dts12
*** rc1 being done as we speak
** 5.7 after that -- Wes
*** needs to start
* Administrative
** Git
*** merging resolving of configure, NEWS, README, ...
*** '''we need a update-these script that protects them'''
*** '''dts12 finished making the makerelease modifications to make it do the right merge -s ours'''
**** '''hardaker will review as a second pair of eyes'''
** Wiki Front Page
* Technical
** Coverity scan results
* Roundtable
** hardaker needs to start a 5.7 branch release
** dts12 needs to finish 5.5/6.2
** magfr needs to finish the transport cleanup
** nba needs to incorporate the BSD patches and push them

Notes20120618

2012-06-18T16:46:14Z

Dts12:

Notes20120402

2012-04-02T18:58:27Z

Dts12: Actually adjust the time as announced here - not just on the admin mailing list

{{meetingtime|time=21|year=2012|month=04|day=02|nextyear=2012|nextmonth=05|nextday=??|prevyear=2012|prevmonth=02|prevday=27}}

* Next Date
* Releases
** 5.5/5.6 -- dts12
** 5.7 after that -- Wes
* Administrative
** Git
*** merging resolving of configure, NEWS, README, ...
*** Add a github repo as well for pull-request patch support? -- Wes
* Technical
** Coverity scan results
* Roundtable

Notes20120116

2012-01-16T19:48:22Z

Dts12:

{{meetingtime|time=19|year=2012|month=01|day=16|nextyear=2012|nextmonth=02|nextday=??|prevyear=2011|prevmonth=12|prevday=19}}

* Next Date
* Releases
** 5.5/5.6 Starting Soon?
** 5.7 after that
* Administrative
** Git
*** changelog generation
*** NEWS/CHANGES
*** email
**** added --no-merges to the update hook
**** could show diffs, but I think that's too large
** Google SOC
* Technical
** Coverity scan results
** --enable-read-only vs --disable-snmp-set
** DisMan Event MIB: monitoring string values
* Roundtable

Notes20120116

2011-12-26T15:44:50Z

Dts12:

{{meetingtime|time=19|year=2012|month=01|day=16|nextyear=2012|nextmonth=02|nextday=??|prevyear=2011|prevmonth=12|prevday=19}}

* Next Date
* Releases
* Administrative
** Git
** Google SOC
* Technical
** --enable-read-only vs --disable-snmp-set
* Roundtable

Administrative Meetings

2011-12-26T15:44:09Z

Dts12: January meeting

The Net-SNMP administrative staff holds meetings on IRC on a regular basis to discuss project issues, goals, etc. The meetings are run on the #net-snmp-admin channel. Anyone can join and participate. To add agenda items, simply add them to the list in the upcoming meetings pages. If you feel the minutes of past meetings are in error, please edit them as appropriate.

== Upcoming Meetings ==

* [[Notes20120116 | 2012-01-16]]

== Notes From Previous Meetings ==

* [[Notes20111219 | 2011-12-19]]
* [[Notes20111024 | 2011-10-24]]
* [[Notes20110926 | 2011-09-26]]
* [[Notes20110808 | 2011-08-08]]
* [[Notes20110620 | 2011-06-20]]
* [[Notes20110523 | 2011-05-23]]
* [[Notes20110425 | 2011-04-25]]
* [[Notes20110321 | 2011-03-21]]
* [[Notes20110221 | 2011-02-21]]
* [[Notes20110131 | 2011-01-31]]
* [[Notes20110103 | 2011-01-03]]
* [[Notes20101129 | 2010-11-29]]
* [[Notes20101011 | 2010-10-11]]
* [[Notes20100920 | 2010-09-20]]
* [[Notes20100809 | 2010-08-09]]
* [[Notes20100607 | 2010-06-07]]
* [[Notes20100517 | 2010-05-17]]
* [[Notes20100419 | 2010-04-19]]
* [[Notes20100315 | 2010-03-15]]
* [[Notes20100222 | 2010-02-22]]
* [[Notes20100111 | 2010-01-11]]
* [[Notes20091214 | 2009-12-14]]
* [[Notes20091116 | 2009-11-16]]
* [[Notes20091012 | 2009-10-12]]
* [[Notes20090914 | 2009-09-14]]
* [[Notes20090810 | 2009-08-10]]
* [[Notes20090720 | 2009-07-20]]
* [[Notes20090615 | 2009-06-15]]
* [[Notes20090518 | 2009-05-18]]
* [[Notes20090406 | 2009-04-06]]
* [[Notes20090302 | 2009-03-02]]
* [[Notes20090202 | 2009-02-02]]
* [[Notes20090105 | 2009-01-05]]
* [[Notes20081110 | 2008-11-10]]
* [[Notes20081006 | 2008-10-06]]
* [[Notes20080915 | 2008-09-15]]
* [[Notes20080811 | 2008-08-11]]
* [[Notes20080707 | 2008-07-07]]
* [[Notes20080602 | 2008-06-02]]
* [[Notes20080509 | 2008-05-09]]
* [[Notes20080331 | 2008-03-31]]
* [[Notes20080211 | 2008-02-11]]
* [[Notes20080115 | 2008-01-15]]
* [[Notes20071211 | 2007-12-11]]
* [[Notes20071114 | 2007-11-14]]
* [[Notes20071009 | 2007-10-09]]
* [[Notes20070919 | 2007-09-19]]
* [[Notes20070823 | 2007-08-23]]
* [[Notes20070719 | 2007-07-19]]
* [[Notes20070705 | 2007-07-05]]
* [[Notes20070601 | 2007-06-01]]
* [[Notes20070511 | 2007-05-11]]
* [[Notes20070406 | 2007-04-06]]
* [[notes20070302 | 2007-03-02]]
* [[notes20070209 | 2007-02-09]]
* [[notes20061222 | 2006-12-22]]
* [[notes20061122 | 2006-11-22]]
* [[notes20061103 | 2006-11-03]]
* [[notes20060928 | 2006-09-28]]
* [[notes20060908 | 2006-09-08]]
* [[notes20060804 | 2006-08-04]]

== Future Topics ==

These items are likely topics for future discussions when time permits:

* The Great Rename (aka "svn move")
** consistent structure
** path names shorter than 100 chars to minimize tar problems
* [[Google SoC]] 2009

== Bug Bash ==

For a while, there were also separate [[BugBash]] meetings on IRC.
However these have fallen into disuse, and have not happened recently.

[[Category:Admin]]

Notes20120116

2011-12-26T15:43:02Z

Dts12: Basic agenda

Notes20110808

2011-08-08T15:52:16Z

Dts12: Spamming of Wiki

{{meetingtime|time=19|year=2011|month=08|day=08|nextyear=2011|nextmonth=09|nextday=??|prevyear=2011|prevmonth=06|prevday=20}}

* Next Meeting
** '''August 1st'''
* Releases
** 5.7.1
** Windows binaries
* Administrative
** GIT
*** rebase vs merge
*** git commit -s --author
*** any general thoughts comments and feedback?
** LTS Timing
*** Need a wiki page describing the cycles and showing examples from [[Notes20110523]]
**** Progress on ''dts12 will create a document''?
** Spamming of Wiki
* Technical
** HR-MIB and RPM
*** follow up?
** numerical extend/exec output
** Architecture Wiki Pages
** Windows patches in the patch tracker
** 6.0?
* Round Table

Notes20110808

2011-08-08T15:50:56Z

Dts12: numerical extend/exec output

{{meetingtime|time=19|year=2011|month=08|day=08|nextyear=2011|nextmonth=09|nextday=??|prevyear=2011|prevmonth=06|prevday=20}}

* Next Meeting
** '''August 1st'''
* Releases
** 5.7.1
** Windows binaries
* Administrative
** GIT
*** rebase vs merge
*** git commit -s --author
*** any general thoughts comments and feedback?
** LTS Timing
*** Need a wiki page describing the cycles and showing examples from [[Notes20110523]]
**** Progress on ''dts12 will create a document''?
* Technical
** HR-MIB and RPM
*** follow up?
** numerical extend/exec output
** Architecture Wiki Pages
** Windows patches in the patch tracker
** 6.0?
* Round Table

Notes20110808

2011-08-08T15:29:14Z

Dts12: Windows binaries

{{meetingtime|time=19|year=2011|month=08|day=08|nextyear=2011|nextmonth=09|nextday=??|prevyear=2011|prevmonth=06|prevday=20}}

* Next Meeting
** '''August 1st'''
* Releases
** 5.7.1
** Windows binaries
* Administrative
** GIT
*** rebase vs merge
*** git commit -s --author
*** any general thoughts comments and feedback?
** LTS Timing
*** Need a wiki page describing the cycles and showing examples from [[Notes20110523]]
**** Progress on ''dts12 will create a document''?
* Technical
** HR-MIB and RPM
*** follow up?
** Architecture Wiki Pages
** Windows patches in the patch tracker
** 6.0?
* Round Table

Template:FAQ:General 06

2011-08-07T21:24:10Z

Dts12: Update O/S version numbers, in line with 5.7 FAQ text

Both the applications and the agent have been reported as running
(at least in part) on the following operating systems:

* Linux (kernels 2.6 to 1.3)
* Solaris/SPARC (11 to 2.3), Solaris/Intel (10, 9) -- see README.solaris
* HP-UX (11.31 to 9.01) -- see README.hpux11
* Mac OS X (10.5 to 10.1) -- see README.osX
* NetBSD (2.0 to 1.0)
* FreeBSD (7.0 to 2.2)
* OpenBSD (4.0 to 2.6)
* BSDi (4.0.1 to 2.1)
* AIX (6.1, 5.3, 5.2, 5.1, 4.3.3, 4.1.5, 3.2.5) -- see README.aix
* IRIX (6.5 to 5.1)
* OSF (4.0, 3.2 and Tru64 Unix 5.1B) -- see README.tru64
* SunOS 4 (4.1.4 to 4.1.2)
* Ultrix (4.5 to 4.2)
* Dynix/PTX 4.4
* QNX 6.2.1A

We have also been informed about a port to the Stratus VOS.
See http://ftp.stratus.com/vos/network/network.html for details.

See the [[FAQ:General_08|next question but one]] for the status of Windows support.

Certain systems fail to compile particular portions of the agent.
These can usually be persuaded to compile (at the loss of some
functionality) by omitting the modules affected.
See the next question for more details.

Also note that the presence of a particular configuration in this
list does not imply a perfect or complete implementation. This
is simply what various people have reported as seeming to work.
(Or more frequently, the configurations where people have reported
problems that we think we've subsequently fixed!)

Git For Developers

2011-06-29T11:00:09Z

Dts12: Clarify choice of modules

[[Git]] is a distributed version control system. This page provides information for developers on how we manage our sources within git.

== Setup ==

git clone ssh://USERNAME@net-snmp.git.sourceforge.net/gitroot/net-snmp/MODULE

where MODULE is either 'net-snmp' (for code) or 'htdocs' (for web documentation)

Make sure your email address and name are correct:

git config user.email "''YOURSFACCOUNTNAME''@users.sourceforge.net"
git config user.name "''YOUR NAME''"

== Git work flows ==

The first link below should be read before any code is checked in. Specifically, it describes the one important aspect: '''always commit to the lowest branch you want the patch to apply to!'''

* First and foremost, read Net-SNMP's [[Git Workflow]]
* Then, consider using the [[Git Branch Management]] macros for performing the routine tasks (branch merging, etc).
* [http://www.kernel.org/pub/software/scm/git/docs/gitworkflows.html The gitworkflows manual page] is similar to ours
* [http://nvie.com/img/2009/12/Screen-shot-2009-12-24-at-11.32.03.png A good diagram] showing another similar workflow pattern.

=== Making changes ===

This is where you type ''vi'' or ''emacs'' or if you're a real developer who likes to get dirty ''perl -i -p -e ...''

=== Checking out the right branch ===

git maintains all the code in a single directory, and lets you switch between the branches in the same directory. This is very very different than SVN and other repository systems, but most people find once they let go of the idea that they need separate directories, they're happier in the long run.

The branch may not exist yet in your local repository (run ''git branch -a'' to list all the branches known, including the remote ones). To start, simply check it out:

# '''git checkout V5-4-patches'''
Branch V5-5-patches set up to track remote branch V5-5-patches from origin.
Switched to a new branch 'V5-5-patches'

(and now 'git branch' without the '-a' will list it as a known local branch).

=== Moving changes to a different branch ===

If you have changes in the local repository already and want to apply them (or test them) against a different branch, the easiest way to do this is with ''stash'' and ''pop'':

# '''git checkout V5-6-patches'''
error: Your local changes to the following files would be overwritten by checkout:
NEWS
Please, commit your changes or stash them before you can switch branches.
Aborting

# '''git stash'''
Saved working directory and index state WIP on V5-5-patches: 6a5e5a6 Merge branch 'V5-4-patches' into V5-5-patches
HEAD is now at 6a5e5a6 Merge branch 'V5-4-patches' into V5-5-patches

# '''git checkout V5-6-patches'''
Branch V5-6-patches set up to track remote branch V5-6-patches from origin.
Switched to a new branch 'V5-6-patches'

# '''git stash pop'''
Auto-merging NEWS
# On branch V5-6-patches
# Changes not staged for commit:
# (use "git add <file>..." to update what will be committed)
# (use "git checkout -- <file>..." to discard changes in working directory)
#
# modified: NEWS
#
no changes added to commit (use "git add" and/or "git commit -a")
Dropped refs/stash@{0} (102700302cd0a9db42b1669105291bb92fe807e9)

=== Committing the changes ===

# git commit -m "commit message" ''FILES''

Or if you want to commit everything in a directory and down, use a directory name instead of ''FILES''.

Or if you want to commit everything anywhere in the repo, use the ''-a'' switch.

'''NOTE:''' this only commits them to your local copy of the repository. This is different than [[SVN]], if you're more familiar with SVN. Next you need to ''push'' them to the master repository:

=== Pulling the latest changes from the upstream ===

Whether or not you've modified files locally and checked in the changes to your local repository, you'll need to occasionally pull down any changes that others have made upstream. You do this with a ''pull''. The --rebase option means rather than treat your development as a parallel set, try and apply your resulting patches to the end of the pulled branch instead of merging them. This tends to keep a cleaner history tree.

# git pull --rebase origin master

Assuming you followed the instructions above, and didn't cloning from somewhere else first, you should be able to shorten this to:

# git pull --rebase

This will merge any changes you've made with any that others have made. If something goes wrong, git will complain about conflicts and you'll need to resolve those either manually or using ''git mergetool''. That's a longer subject for another lesson: [[Git Merging]].

You may also wish to pull all the remote branches:

# git pull --all

=== Pushing the changes upstream ===

Once you're sure your commits are safe themselves and you've updated your repo with the latest upstream you can push your changes upstream to the master repository on sourceforge:

# git push origin master

Assuming you followed the instructions above, and didn't cloning from somewhere else first, you should be able to shorten this to:

# git push

And you're done!

=== Notes on the htdocs repository ===

The ''htdocs'' module, which contains the Net-SNMP website, is only synchronized from the git repository once an hour. It may take up to an hour before the changes take effect on the website.

== Creating tags and branches ==

=== Tagging ===

Tags are simply a symbolic way of remembering "a point in time" that is easier than the sha1 hash that is more frequently seen.

git tag my-really-super-feature-works

for example will create the above tag.

'''XXX: discuss annotated/signed/etc tags'''

=== Pushing tags ===

By default, ''git push'' doesn't push tags. IE, it *only* pushes code. If you've created a tag and you want it pushed upstream, you'll need to push it manually:

git push origin ''TAGNAME''

Or you can push '''all your tags''':

git push --tags

Note: Please don't push personal tags... Use the individual push instead if you're creating helpful personal tags.

[[Category:Git]]

Template:TUT:LIST

2011-04-14T07:40:51Z

Dts12: Reverted edits by Johndavid486 (talk) to last revision by Rstory

== Tutorial Sections ==

=== About the SNMP Protocol ===
These tutorial links talk about SNMP generically and how the protocol itself works. They are good introductory reading material and the concepts are important to understand before diving into the later tutorials about Net-SNMP itself.
* [[TUT:SNMP | How SNMP Works]]: About the protocol itself (GETs, GETNEXTs, etc)
* [[TUT:MIBs | What data is in SNMP]]: All about SNMP ''Management Information Bases'' (MIBs)
* [[TUT:Security | Securing SNMP]]: How to use the SNMP protocol securely

=== Net-SNMP Command Line Applications ===
These tutorial pages discuss the command line tools provided in the Net-SNMP suite of tools. Nearly all the example commands in these tutorials works if you try it yourself, as they're all examples that talk to our online Net-SNMP test agent. Given them a shot!
* [[TUT:snmptranslate | snmptranslate]]: learning about the MIB tree.
* [[TUT:snmpget | snmpget]]: retrieving data from a host.
* [[TUT:snmpgetnext | snmpgetnext]]: retrieving unknown indexed data.
* [[TUT:snmpwalk | snmpwalk]]: retrieving lots of data at once!
* [[TUT:snmptable | snmptable]]: displaying a table.
* [[TUT:snmpset | snmpset]]: peforming write operations.
* [[TUT:snmpbulkget | snmpbulkget]]: communicates with a network entity using SNMP GETBULK request
* [[TUT:snmpbulkwalk | snmpbulkwalk]]: retrieve a sub-tree of management values using SNMP GETBULK requests.
* [[TUT:snmptrap | snmptrap]]: Sending and receiving traps, and acting upon them.
** [[TUT:snmptrap_SNMPv3 | Traps/informs with SNMPv3/USM]]: Sending and receiving SNMPv3/USM TRAPs and INFORMs
** [[TUT:agentxtrap | Sending Traps/Informs via AgentX]]: Sending notifications from the command line through snmpd
* Common command line options:
** [[TUT:Using and loading MIBS | Using and loading MIBS]]
** [[TUT:SNMPv3 Options | SNMPv3/USM Options]]
** [[TUT:Using TLS | Using SNMPv3 over TLS and DTLS]]
** [[TUT:Customized Output Formats | Customized Output Formats]]
* [[TUT:mib2c config files | Writing mib2c config files ]]

=== Application Configuration ===
All of our applications support configuration to allow you to customize how they behave.
* [[TUT:Configuring Net-SNMP Applications | Configuration files for Net-SNMP applications]]

=== Net-SNMP Daemons ===
Net-SNMP comes with two long-running daemons: a SNMP agent (''[[snmpd]]'') for responding to management requests and a notification receiver (''[[snmptrapd]]'') for receiving SNMP notifications.
* SNMP Agent (snmpd) Configuration
** [[TUT:snmpd configuration|Configuration Basics]]
** [[Vacm | Access Control (VACM)]]
** [[snmpconf]]
* SNMP Notification Receiver (snmptrapd)
** [[TUT:Configuring snmptrapd|Configuring snmptrapd]]
** [[TUT:Configuring snmptrapd to receive SNMPv3 notifications|Configuring SNMPv3 notifications]]
** [[TUT:Configuring snmptrapd to parse MIBS from 3rd party Vendors|Configuring snmptrapd to understand vendor-specific MIBS (Cisco)]]
* Agent Monitoring
** [[TUT:DisMan Monitoring|DisMan Monitoring]]
** [[TUT:MRTG|Monitoring with MRTG]]

=== Coding Tutorials ===
Net-SNMP comes with a highly flexible and extensible API. The API allows you to create your own commands, add extensions to the agent to support your own [[MIB|MIBs]] and perform specialized processing of notifications.
* Client / Manager Coding Tutorials
** [[TUT:Simple Application|Writing a simple application]]
** [[TUT:Simple Async Application|Writing a simple asynchronous application]]
* Agent Coding Tutorials
** [[TUT:Writing a MIB Module | Writing a mib module]] to serve information described by an SNMP MIB, and how to compile it into the net-snmp snmpd agent.
** [[TUT:Writing a Dynamically Loadable Object | Writing a Dynamically Loadable Object]] that can be loaded into the SNMP agent.
** [[TUT:Writing a Subagent | Writing a Subagent]] that can be run to attach to the snmpd master agent.
** [[Tut:Extending snmpd using perl | Writing a perl plugin to extend the agent]] using the NetSNMP::agent module.
** [[Tut:Extending_snmpd_using_shell_scripts | Writing shell scripts to extend the agent]]
** Using mib2c to help write an agent code template for you
*** [[TUT:mib2c General Overview | General mib2c Overview]]
*** [[TUT:mib2c-update | Using the mib2c-update script to ''recode'' your code]]
*** [http://www.net-snmp.org/tutorial/tutorial-5/toolkit/mfd/ mib2c.mfd.conf tutorial]
* [[TUT:Header files|Header files and autoconf]]

=== Debugging SNMP Applications and Agents ===
All our tools and applications have extensive debugging output. These tutorials talk about how the debugging system works and how you can add your own debugging statements to you code:
* [[Debugging output | Debugging output printed using the -D command line option]]
** [[DEBUGMSG | Putting DEBUGMSG tokens in your code]]
* [[Debugging packet traces | Using -Ddump to display packet breakdowns]]
* [[Debugger|Debugging using GDB]]

=== Operating System Specific Tutorials ===
* Building With Visual Studio 2005 Express
** [[Using the command line and nmake]]
* [[Net-Snmp on Ubuntu]]
* [[Net-SNMP and lm-sensors on Ubuntu 10.04]]

Template:FAQ:Compiling 07

2011-03-10T08:30:41Z

Dts12: Clarify that v5.7 is not yet available

In order to reduce the memory footprint (for instance, to
embed the snmpd into a device), the following configure options
could be used.

'--disable-debugging'
This turns off the compilation of all debugging statements.

'--enable-mini-agent' '--with-out-mib-modules=examples/ucdDemoPublic'
This creates an agent with just the essential MIB modules included.
With the release of Net-SNMP 5.7 (currently in development), you will be able to use
'--with-out-mib-modules=default_modules'
to reduce the size a little further.
NOTE: If you need additional MIB modules, then simply add them
using the option <CODE>'--with-mib-modules=...'</CODE> but this will of course
increase the memory footprint.

'--with-transports=UDP'
This option specifies the transport domains to include.
For a simple standalone agent, just UDP should be sufficient.
(Although the <CODE>'disman'</CODE> and <CODE>'agentx'</CODE> modules may require the
Callback, TCP and/or Unix transport domains as well).

'--without-kmem-usage'
This can be used in order to omit the code that operates on the
/dev/kmem interface. Clearly, this option cannot be used when
one of the configured MIB modules depends on it.

'--with-mibdirs=' and '--with-mibs='
These options tell the agent not to load any MIB modules.
This doesn't affect the size of libraries or application
binaries, but will reduce the memory footprint during runtime.

'--disable-mib-loading'
This can be used in order to omit the code that loads and
parses the MIB files altogether. This will reduce both the
runtime memory footprint, and the binary sizes.

'--without-opaque-special-types'
This disables an extension (double, float and signed 64-bit types) to
the snmp protocol that isn't strictly necessary. This option disables the
extension and all the code that operate on it.

Once the agent (snmpd) has been linked, you might also try running
<CODE>'strip snmpd'</CODE> to remove un-necessary debug/symbol information.

Template:TUT:LIST

2011-03-09T12:48:49Z

Dts12: Reverted edits to last revision by Ckmac97

== Tutorial Sections ==

=== About the SNMP Protocol ===
These tutorial links talk about SNMP generically and how the protocol itself works. They are good introductory reading material and the concepts are important to understand before diving into the later tutorials about Net-SNMP itself.
* [[TUT:SNMP | How SNMP Works]]: About the protocol itself (GETs, GETNEXTs, etc)
* [[TUT:MIBs | What data is in SNMP]]: All about SNMP ''Management Information Bases'' (MIBs)
* [[TUT:Security | Securing SNMP]]: How to use the SNMP protocol securely

=== Net-SNMP Command Line Applications ===
These tutorial pages discuss the command line tools provided in the Net-SNMP suite of tools. Nearly all the example commands in these tutorials works if you try it yourself, as they're all examples that talk to our online Net-SNMP test agent. Given them a shot!
* [[TUT:snmptranslate | snmptranslate]]: learning about the MIB tree.
* [[TUT:snmpget | snmpget]]: retrieving data from a host.
* [[TUT:snmpgetnext | snmpgetnext]]: retrieving unknown indexed data.
* [[TUT:snmpwalk | snmpwalk]]: retrieving lots of data at once!
* [[TUT:snmptable | snmptable]]: displaying a table.
* [[TUT:snmpset | snmpset]]: peforming write operations.
* [[TUT:snmpbulkget | snmpbulkget]]: communicates with a network entity using SNMP GETBULK request
* [[TUT:snmpbulkwalk | snmpbulkwalk]]: retrieve a sub-tree of management values using SNMP GETBULK requests.
* [[TUT:snmptrap | snmptrap]]: Sending and receiving traps, and acting upon them.
** [[TUT:snmptrap_SNMPv3 | Traps/informs with SNMPv3/USM]]: Sending and receiving SNMPv3/USM TRAPs and INFORMs
** [[TUT:agentxtrap | Sending Traps/Informs via AgentX]]: Sending notifications from the command line through snmpd
* Common command line options:
** [[TUT:Using and loading MIBS | Using and loading MIBS]]
** [[TUT:SNMPv3 Options | SNMPv3/USM Options]]
** [[TUT:Using TLS | Using SNMPv3 over TLS and DTLS]]
** [[TUT:Customized Output Formats | Customized Output Formats]]
* [[TUT:mib2c config files | Writing mib2c config files ]]

=== Application Configuration ===
All of our applications support configuration to allow you to customize how they behave.
* [[TUT:Configuring Net-SNMP Applications | Configuration files for Net-SNMP applications]]

=== Net-SNMP Daemons ===
Net-SNMP comes with two long-running daemons: a SNMP agent (''[[snmpd]]'') for responding to management requests and a notification receiver (''[[snmptrapd]]'') for receiving SNMP notifications.
* SNMP Agent (snmpd) Configuration
** [[TUT:snmpd configuration|Configuration Basics]]
** [[Vacm | Access Control (VACM)]]
** [[snmpconf]]
* SNMP Notification Receiver (snmptrapd)
** [[TUT:Configuring snmptrapd|Configuring snmptrapd]]
** [[TUT:Configuring snmptrapd to receive SNMPv3 notifications|Configuring SNMPv3 notifications]]
** [[TUT:Configuring snmptrapd to parse MIBS from 3rd party Vendors|Configuring snmptrapd to understand vendor-specific MIBS (Cisco)]]
* Agent Monitoring
** [[TUT:DisMan Monitoring|DisMan Monitoring]]
** [[TUT:MRTG|Monitoring with MRTG]]

=== Coding Tutorials ===
Net-SNMP comes with a highly flexible and extensible API. The API allows you to create your own commands, add extensions to the agent to support your own [[MIB|MIBs]] and perform specialized processing of notifications.
* Client / Manager Coding Tutorials
** [[TUT:Simple Application|Writing a simple application]]
** [[TUT:Simple Async Application|Writing a simple asynchronous application]]
* Agent Coding Tutorials
** [[TUT:Writing a MIB Module | Writing a mib module]] to serve information described by an SNMP MIB, and how to compile it into the net-snmp snmpd agent.
** [[TUT:Writing a Dynamically Loadable Object | Writing a Dynamically Loadable Object]] that can be loaded into the SNMP agent.
** [[TUT:Writing a Subagent | Writing a Subagent]] that can be run to attach to the snmpd master agent.
** [[Tut:Extending snmpd using perl | Writing a perl plugin to extend the agent]] using the NetSNMP::agent module.
** Using mib2c to help write an agent code template for you
*** [[TUT:mib2c General Overview | General mib2c Overview]]
*** [[TUT:mib2c-update | Using the mib2c-update script to ''recode'' your code]]
*** [http://www.net-snmp.org/tutorial/tutorial-5/toolkit/mfd/ mib2c.mfd.conf tutorial]
* [[TUT:Header files|Header files and autoconf]]

=== Debugging SNMP Applications and Agents ===
All our tools and applications have extensive debugging output. These tutorials talk about how the debugging system works and how you can add your own debugging statements to you code:
* [[Debugging output | Debugging output printed using the -D command line option]]
** [[DEBUGMSG | Putting DEBUGMSG tokens in your code]]
* [[Debugging packet traces | Using -Ddump to display packet breakdowns]]
* [[Debugger|Debugging using GDB]]

=== Operating System Specific Tutorials ===
* Building With Visual Studio 2005 Express
** [[Using the command line and nmake]]
* [[Net-Snmp on Ubuntu]]
* [[Net-SNMP and lm-sensors on Ubuntu 10.04]]

Template:TUT:LIST

2011-03-09T12:45:24Z

Dts12: Reverted edits by Allensmith (talk) to last revision by Alysia101

== Tutorial Sections ==

=== About the SNMP Protocol ===
These tutorial links talk about SNMP generically and how the protocol itself works. They are good introductory reading material and the concepts are important to understand before diving into the later tutorials about Net-SNMP itself.
* [[TUT:SNMP | How SNMP Works]]: About the protocol itself (GETs, GETNEXTs, etc)
* [[TUT:MIBs | What data is in SNMP]]: All about SNMP ''Management Information Bases'' (MIBs)
* [[TUT:Security | Securing SNMP]]: How to use the SNMP protocol securely

=== Net-SNMP Command Line Applications ===
These tutorial pages discuss the command line tools provided in the Net-SNMP suite of tools. Nearly all the example commands in these tutorials works if you try it yourself, as they're all examples that talk to our online Net-SNMP test agent. Given them a shot!
* [[TUT:snmptranslate | snmptranslate]]: learning about the MIB tree.
* [[TUT:snmpget | snmpget]]: retrieving data from a host.
* [[TUT:snmpgetnext | snmpgetnext]]: retrieving unknown indexed data.
* [[TUT:snmpwalk | snmpwalk]]: retrieving lots of data at once!
* [[TUT:snmptable | snmptable]]: displaying a table.
* [[TUT:snmpset | snmpset]]: peforming write operations.
* [[TUT:snmpbulkget | snmpbulkget]]: communicates with a network entity using SNMP GETBULK request
* [[TUT:snmpbulkwalk | snmpbulkwalk]]: retrieve a sub-tree of management values using SNMP GETBULK requests.
* [[TUT:snmptrap | snmptrap]]: Sending and receiving traps, and acting upon them.
** [[TUT:snmptrap_SNMPv3 | Traps/informs with SNMPv3/USM]]: Sending and receiving SNMPv3/USM TRAPs and INFORMs
** [[TUT:agentxtrap | Sending Traps/Informs via AgentX]]: Sending notifications from the command line through snmpd
* Common command line options:
** [[TUT:Using and loading MIBS | Using and loading MIBS]]
** [[TUT:SNMPv3 Options | SNMPv3/USM Options]]
** [[TUT:Using TLS | Using SNMPv3 over TLS and DTLS]]
** [[TUT:Customized Output Formats | Customized Output Formats]]
* [[TUT:mib2c config files | Writing mib2c config files ]]

=== Application Configuration ===
All of our applications support configuration to allow you to customize how they behave.
* [[TUT:Configuring Net-SNMP Applications | Configuration files for Net-SNMP applications]]

=== Net-SNMP Daemons ===
Net-SNMP comes with two long-running daemons: a SNMP agent (''[[snmpd]]'') for responding to management requests and a notification receiver (''[[snmptrapd]]'') for receiving SNMP notifications.
* SNMP Agent (snmpd) Configuration
** [[TUT:snmpd configuration|Configuration Basics]]
** [[Vacm | Access Control (VACM)]]
** [[snmpconf]]
* SNMP Notification Receiver (snmptrapd)
** [[TUT:Configuring snmptrapd|Configuring snmptrapd]]
** [[TUT:Configuring snmptrapd to receive SNMPv3 notifications|Configuring SNMPv3 notifications]]
** [[TUT:Configuring snmptrapd to parse MIBS from 3rd party Vendors|Configuring snmptrapd to understand vendor-specific MIBS (Cisco)]]
* Agent Monitoring
** [[TUT:DisMan Monitoring|DisMan Monitoring]]
** [[TUT:MRTG|Monitoring with MRTG]]

=== Coding Tutorials ===
Net-SNMP comes with a highly flexible and extensible API. The API allows you to create your own commands, add extensions to the agent to support your own [[MIB|MIBs]] and perform specialized processing of notifications.
* Client / Manager Coding Tutorials
** [[TUT:Simple Application|Writing a simple application]]
** [http://www.merchantos.com pos software]
** [[TUT:Simple Async Application|Writing a simple asynchronous application]]
* Agent Coding Tutorials
** [[TUT:Writing a MIB Module | Writing a mib module]] to serve information described by an SNMP MIB, and how to compile it into the net-snmp snmpd agent.
** [[TUT:Writing a Dynamically Loadable Object | Writing a Dynamically Loadable Object]] that can be loaded into the SNMP agent.
** [[TUT:Writing a Subagent | Writing a Subagent]] that can be run to attach to the snmpd master agent.
** [[Tut:Extending snmpd using perl | Writing a perl plugin to extend the agent]] using the NetSNMP::agent module.
** Using mib2c to help write an agent code template for you
*** [[TUT:mib2c General Overview | General mib2c Overview]]
*** [[TUT:mib2c-update | Using the mib2c-update script to ''recode'' your code]]
*** [http://www.net-snmp.org/tutorial/tutorial-5/toolkit/mfd/ mib2c.mfd.conf tutorial]
* [[TUT:Header files|Header files and autoconf]]

=== Debugging SNMP Applications and Agents ===
All our tools and applications have extensive debugging output. These tutorials talk about how the debugging system works and how you can add your own debugging statements to you code:
* [[Debugging output | Debugging output printed using the -D command line option]]
** [[DEBUGMSG | Putting DEBUGMSG tokens in your code]]
* [[Debugging packet traces | Using -Ddump to display packet breakdowns]]
* [[Debugger|Debugging using GDB]]

=== Operating System Specific Tutorials ===
* Building With Visual Studio 2005 Express
** [[Using the command line and nmake]]
* [[Net-Snmp on Ubuntu]]
* [[Net-SNMP and lm-sensors on Ubuntu 10.04]]

Release Instructions

2011-03-01T16:18:09Z

Dts12: Restructure Linux RPMs description

This page documents varios aspects of creating releases and binary builds suitable for distribution of the project products:

= Releasing Source Code =

== MakeRelease ==
The current release procedures are reliant on the [http://makerelease.sourceforge.net/ MakeRelease] system,
which is designed to automate (and document) as much of the process as possible.

MakeRelease can be installed as follows:

<code>
svn co https://makerelease.svn.sourceforge.net/svnroot/makerelease/trunk/makerelease makerelease
cd makerelease
perl Makefile.PL
make
sudo make install
</code>

== Preliminary tasks ==

Before you start, check that the installed versions of <code>autoconf</code>,
<code>automake</code> and <code>libtool</code> match the requirements for this branch
(as listed under [[Build_System#Tool_Versions]])

If the release is being built from a fresh SVN checkout,
then you should run <code>configure</code> by hand
'''before''' running <code>makerelease</code>.
This is because the release process relies on running various
<code>make</code> commands before invoking <code>configure</code> itself,
and expects there to be a suitable <code>Makefile</code> already present.

== Building a Source Release ==

In order to start packaging up a new release,
change directory to the root of the code tree to be released
(which should be under SVN control), and run the command:

<code>
makerelease -c dist/makerelease.xml
</code>

Most of the process is automated, and will be performed automatically,
with the script simply stopping at regular intervals to allow you to
verify what is being done.

There are two main steps where manual intervention is required:

* Step 4.4 - trim the file <code>ChangeLog.reallyadd</code> to contain ''just'' those changes applied since the last run of <code>makerelease</code>, and then to include these changes into the main <code>ChangeLog</code> file.

* Step 4.8 - merge the contents of <code>CHANGES.new2</code> into <code>CHANGES</code> (and similarly for <code>NEWS</code>)

Note that it's worth spending some time on this step.
Although most of the significant changes will hopefully have been tagged when they were commited,
and should be extracted automatically, the descriptions are sometimes truncated or unclear.
The release manager is also usually in a good position to judge the relative importance of
various changes, so should move descriptions between the <code>CHANGES</code> and <code>NEWS</code> files

== Notes ==

If a release is built from a 'clean' source tree, where configure has never been run (or not run since a "make distclean"),
then Step 2.3 ("make docs" and "make mancp"), and Step 3.1 ("make distclean") will fail.
These failures are not significant, and the process can be allowed to continue.

If a second release is made from the same source tree, make sure that you remove the previous 'net-snmp-{version}' directory first. Otherwise this will confuse Step 4.2 ("make depend")

There are a few other steps where manual intervention is sometimes needed
(or may appear to be!)

* Step 1.2 - specify the version number for this release
* Step 2.1.1 - the library version numbers will normally only need to be tweaked for the first (.pre1) version of a given release cycle
* Step 2.3 - extracting the in-line documentation will typically generate a '''large''' number of warnings. These can safely be ignored
* Step 2.5 - there may also be a number of "new" function man pages, which are not under SVN control These can also be ignored - there is no need to run <code>svn add</code> on them. (In fact, the automatic generation of these man pages should probably be disabled altogether)
* Step 3.4 - the <code>make checks</code> test invariably fails The complaint about non-portable constructs in the top-level <code>Makefile.in</code> file can be ignored - other errors should be taken on their merits It will usually be necessary to explicitly '''c'''ontinue at this point
* Step 4.1 - the <code>make depend</code> step will generate a large number of warnings - these can safely be ignored

* Steps 5.8 and 5.10 - If you don't have the Net-SNMP Administration secret key (or can't remember the password!), you'll have to skip these signing steps. MD5 checksums (or full package signatures) can be generated and uploaded at a later date

== Publishing and Advertising ==

From Step 6 onwards, the process relies more on manual intervention, with relatively little being automated.
The <code>makerelease</code> script will guide you through what is required, but won't actually perform most of these actions.

* Step 6.1 - note that the example command uses Wes' SourceForge account details. Amend <code>hardaker</code> to be your SF login name.

* Step 6.2 - updating the Download web page needs to be done via the SVN repository

* Steps 6.3, 8.1, 8.4 - these attempt to open the relevant web pages for editing, but this may well fail - update the relevant pages manually (or ignore them), and '''c'''ontinue

= Producing Binaries =

== Linux RPMs ==

There are two elements to generating a set of RPM binaries - deciding
on the structure of the RPMs to create (which is controlled by the contents
of the <code>net-snmp.spec</code> file), and actually generating these RPMs.

=== Traditional Net-SNMP RPM structure ===

Historically, the Net-SNMP project has tended to distribute just three binary RPMs:
* net-snmp (the main RPM, containing both client-utilities and the agent, together with the supporting framework)
* net-snmp-devel (header files and archive libraries, needed for developing new SNMP applications)
* net-snmp-perlmods (the perl modules)

This structure uses the RPM spec file that is included as part of the source code tree,
in <code>dist/net-snmp.spec</code>.

The spec file also attempts to include suitable "provide" definitions which should
allow these RPMs to replace the vendor-supplied Net-SNMP RPMs which come with
SuSE-based and RedHat-based systems (including RHEL, Fedora and CentOS distributions).

=== RedHat/Fedora RPM structure ===

RedHat-based distributions tend to use a larger number of individual RPMs,
allowing system administrators to select which elements to install
(e.g. SNMP clients without the SNMP agent, or vice versa).

* net-snmp (the SNMP agent)
* net-snmp-utils (the command-line client applications)
* net-snmp-libs (shared libraries and other supporting framework)
* net-snmp-devel (header files and libraries, needed for developing new SNMP applications)
* net-snmp-perl (the perl modules)
* net-snmp-python (the python modules)
* net-snmp-gui (tkmib)

This uses the RPM spec file from the Fedora repository,
which can be retrieved (together with accompanying files)
using the command <code>git clone git://pkgs.fedoraproject.org/net-snmp</code>

Note that this spec file includes RedHat-supplied patches to the code,
which may not necessarily be relevant to the version you are
working with. You may need to comment out some of the <code>PatchN</code>
definitions, and the corresponding <code>%patchN</code> setup directives.
It may also be necessary to amend the configure options used, and other
aspects of the spec file, depending on the versions involved.

=== Building RPMs using rpmbuild ===

The traditional approach for generating RPMs uses the command <code>rpmbuild</code>
(part of the RPM <code>rpm-build</code>)

The procedure is as follows:
* Create <code>$HOME/rpmbuild/SPECS</code> and copy the spec file there
* Create <code>$HOME/rpmbuild/SOURCES</code> and copy the tarball there
* If there are any patch files mentioned in the spec file, copy these to <code>$HOME/rpmbuild/SOURCES</code> as well
* Ensure <code>Version</code> in the spec file matches the version of the tarball
* Append a suitable vendor identifier to the <code>Release</code> in the spec file
* Run the command <code>rpmbuild -ba $HOME/rpmbuild/SPECS/net-snmp.spec</code>

This produces the appropriate binary RPM files (under <code>$HOME/rpmbuild/RPMs</code>)
together with a source RPM file (under <code>$HOME/rpmbuild/SRPMs</code>)

=== Building Fedora RPMs ===

Fedora-based distributions can also use the command <code>fedpkg</code>
(part of the RPM <code>fedpkg</code>)

* copy the spec file, source tarball and any patch files into a suitable working directory
* Ensure <code>Version</code> in the file <code>net-snmp/net-snmp.spec</code> matches the version of the tarball
* Run the command <code>fedpkg local</code>

(This procedure may also require the RPM <code>chrpath</code> to be installed)

== Linux DEBs ==

== Solaris ==

* SYSV packages
** see dist/net-snmp-solaris-build
* tar balls
** to be unpacked beneath /usr/local

== Windows ==

TUT:Using and loading MIBS

2011-03-01T15:45:14Z

Dts12: Reverted edits by Randybosh (talk) to last revision by Wes

== Using local MIBs ==

The net-snmp tools can translate numeric object identifies
(OIDs) into textual object identifiers using the MIB description
files. The net-snmp toolkit provides a few of the standard
MIBs, but certainly doesn't contain all the MIBs known to man.

First off, you should know about the paths that the tools load
MIBs from. By default, it loads things from the following list
of directories:

# $HOME/.snmp/mibs
# /usr/local/share/snmp/mibs

Note that many distributions change the default paths. To find out
which directories are used on your system, run the following command:

net-snmp-config --default-mibdirs

(if that doesn't work because your distribution didn't repackage net-snmp-config you can use this instead:)

snmptranslate -Dinit_mib .1.3 2>&1 |grep MIBDIR

So, lets say you have a MIB called
[ftp://ftp.cisco.com/pub/mibs/v2/CISCO-RHINO-MIB.my CISCO-RHINO-MIB]
that you want parsed (it really exists, and I particularly liked
the name so I'm using it in the tutorial). Place the file in
one of the above two directories. If you pulled it from another
file (like an RFC), make sure it doesn't contain anything
non-MIB related (like the text leading up to it, and the page
separators). The very first line in the file should begin with
something like "CISCO-RHINO-MIB DEFINITIONS ::= BEGIN", and the
very last line of the file should be "END"

Now, pick a node in the file that you want to translate that
currently isn't being translated. From the CISCO-RHINO-MIB, I'll
pick the ciscoLS1010ChassisFanLed node.

First, lets verify that our handy snmptranslate command
(discussed [[TUT:snmptranslate|snmptranslate]]) doesn't
yet know about this node:

% '''snmptranslate -IR -On ciscoLS1010ChassisFanLed'''
Unknown object identifier: ciscoLS1010ChassisFanLed

Nope, it doesn't. So, first we need to download the [ftp://ftp.cisco.com/pub/mibs/v2/CISCO-RHINO-MIB.my CISCO-RHINO-MIB]
file and place it in a directory that our snmp tools can find it
in. So, I'm going to place the file in $HOME/.snmp/mibs.

Now, lets use the ''-m'' flag to snmptranslate to tell it to
load that mib. We'll use ''"-m +CISCO-RHINO-MIB"'' to indicate that
we want the tool to load not only the default set of mibs, but the
CISCO-RHINO-MIB as well (the leading '+' plus means "also").

'''% snmptranslate -m +CISCO-RHINO-MIB -IR -On ciscoLS1010ChassisFanLed'''
Cannot find module (CISCO-SMI): At line 31 in $HOME/.snmp/mibs/CISCO-RHINO-MIB.my
Unlinked OID in CISCO-RHINO-MIB: ciscoLS1010ChassisMIB ::= { workgroup 11 }
Cannot adopt OID in CISCO-RHINO-MIB: ciscoAtmSwitchInvalidCellHeader ::= { ciscoAtmSwitchInvalidCellHeaderEntry 2 }
''... rest of output truncated ...''

Wait a minute... What the heck is all that stuff? Errors! Well,
the first line is the most important and it's telling us that we're
missing the CISCO-SMI MIB as well. So, if we go
[ftp://ftp.cisco.com/pub/mibs/v2/CISCO-SMI.my download that MIB file]
and place it in our $HOME/.snmp/mibs directory as
well the command should suddenly work:

% '''snmptranslate -m +CISCO-RHINO-MIB -IR -On ciscoLS1010ChassisFanLed'''
.1.3.6.1.4.1.9.5.11.1.1.12

'''Success!'''

One last comment: You can also force loading of a given MIB and
its node in one fell swoop (and this method is the one most highly
recommended by Niels Baggesen, one of our primary core
developers):

% '''snmptranslate -On CISCO-RHINO-MIB::ciscoLS1010ChassisFanLed'''
.1.3.6.1.4.1.9.5.11.1.1.12

So, there you have it. A complete example for how to get your
own ''insert-spiffy-mib-here'' loaded into the net-snmp tools.

=== Yes, but how do I make it happen all the time? ===

Good question. And of course, we have multiple options for you.
We support a number of ways of doing this.

* First, you can put the following lines in a snmp.conf file. This file can be placed in the system-wide configuration location (EG, ''/usr/local/share/snmp.conf'') or in a personal file (EG, $HOME/.snmp/snmp.conf). The system-wide configuration file location will depend on how Net-SNMP was built on your system. Run '''net-snmp-config --snmpconfpath''' to display the list of paths.

mibs +CISCO-RHINO-MIB
mibs +SOME-OTHER-SPIFFY-MIB

* You can also use the MIBS environment variable to specify things (example assumes a /bin/sh style shell):

MIBS=+CISCO-RHINO-MIB:SOME-OTHER-SPIFFY-MIB
export MIBS

* For the brave you can load all MIB files in your system-wide location - This can save you time, but may give you errors as shown below.

To snmp.conf:

mibs +ALL

And to run it:

'''% snmpwalk -v2c public 192.168.1.100'''
Warning: Module MAU-MIB was in /usr/share/snmp/mibs//DOT3-MAU-MIB.txt now is /usr/share/snmp/mibs//RFC2668-MIB.txt
Warning: Module DISMAN-EVENT-MIB was in /usr/share/snmp/mibs//EVENT-MIB.txt now is /usr/share/snmp/mibs//DISMAN-EVENT-MIB.txt
Warning: Module P-BRIDGE-MIB was in /usr/share/snmp/mibs//P-BRIDGE-MIB.txt now is /usr/share/snmp/mibs//P-BRIDGE.txt

Although, with enabling so many SNMP MIBs at once comes a consequence as seen above. Pipe the stderr to null for cleaner output.

'''% snmpwalk -v2c public 192.168.1.100 2>/dev/null'''
SNMPv2-MIB::sysDescr.0 = STRING: Linux server1 2.4.34-pre2 #170 Fri Sep 15 20:10:21 CEST 2006 mips
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-TC::linux
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (706980) 1:57:49.80

==== Ethereal/Wireshark Notes ====

Note to [http://www.wireshark.org/ Wireshark] users (previously known as ''Ethereal''):

You must use one of these methods in this section for Wireshark
since it won't support the -m and -M options discussed previously.

== See Also ==

Please note the following sections of the FAQ as well:
* [http://www.net-snmp.org/FAQ.html#How_do_I_add_a_MIB_ How do I add a MIB]
* [http://www.net-snmp.org/FAQ.html#How_do_I_add_a_MIB_to_the_tools_ How do I add a MIB to the tools?]
* [http://www.net-snmp.org/FAQ.html#I_m_getting_answers__but_they_re_all_numbers__Why_ I'm getting answers, but they're all numbers. Why?]
* ... (Read the entire [http://www.net-snmp.org/FAQ.html FAQ] Please!)
* [[Writing your own MIBs]]

{{TUT:LIST}}

Release Instructions

2011-02-25T13:55:46Z

Dts12: Expand on producing Fedora-style RPMs

This page documents varios aspects of creating releases and binary builds suitable for distribution of the project products:

= Releasing Source Code =

== MakeRelease ==
The current release procedures are reliant on the [http://makerelease.sourceforge.net/ MakeRelease] system,
which is designed to automate (and document) as much of the process as possible.

MakeRelease can be installed as follows:

<code>
svn co https://makerelease.svn.sourceforge.net/svnroot/makerelease/trunk/makerelease makerelease
cd makerelease
perl Makefile.PL
make
sudo make install
</code>

== Preliminary tasks ==

Before you start, check that the installed versions of <code>autoconf</code>,
<code>automake</code> and <code>libtool</code> match the requirements for this branch
(as listed under [[Build_System#Tool_Versions]])

If the release is being built from a fresh SVN checkout,
then you should run <code>configure</code> by hand
'''before''' running <code>makerelease</code>.
This is because the release process relies on running various
<code>make</code> commands before invoking <code>configure</code> itself,
and expects there to be a suitable <code>Makefile</code> already present.

== Building a Source Release ==

In order to start packaging up a new release,
change directory to the root of the code tree to be released
(which should be under SVN control), and run the command:

<code>
makerelease -c dist/makerelease.xml
</code>

Most of the process is automated, and will be performed automatically,
with the script simply stopping at regular intervals to allow you to
verify what is being done.

There are two main steps where manual intervention is required:

* Step 4.4 - trim the file <code>ChangeLog.reallyadd</code> to contain ''just'' those changes applied since the last run of <code>makerelease</code>, and then to include these changes into the main <code>ChangeLog</code> file.

* Step 4.8 - merge the contents of <code>CHANGES.new2</code> into <code>CHANGES</code> (and similarly for <code>NEWS</code>)

Note that it's worth spending some time on this step.
Although most of the significant changes will hopefully have been tagged when they were commited,
and should be extracted automatically, the descriptions are sometimes truncated or unclear.
The release manager is also usually in a good position to judge the relative importance of
various changes, so should move descriptions between the <code>CHANGES</code> and <code>NEWS</code> files

== Notes ==

If a release is built from a 'clean' source tree, where configure has never been run (or not run since a "make distclean"),
then Step 2.3 ("make docs" and "make mancp"), and Step 3.1 ("make distclean") will fail.
These failures are not significant, and the process can be allowed to continue.

If a second release is made from the same source tree, make sure that you remove the previous 'net-snmp-{version}' directory first. Otherwise this will confuse Step 4.2 ("make depend")

There are a few other steps where manual intervention is sometimes needed
(or may appear to be!)

* Step 1.2 - specify the version number for this release
* Step 2.1.1 - the library version numbers will normally only need to be tweaked for the first (.pre1) version of a given release cycle
* Step 2.3 - extracting the in-line documentation will typically generate a '''large''' number of warnings. These can safely be ignored
* Step 2.5 - there may also be a number of "new" function man pages, which are not under SVN control These can also be ignored - there is no need to run <code>svn add</code> on them. (In fact, the automatic generation of these man pages should probably be disabled altogether)
* Step 3.4 - the <code>make checks</code> test invariably fails The complaint about non-portable constructs in the top-level <code>Makefile.in</code> file can be ignored - other errors should be taken on their merits It will usually be necessary to explicitly '''c'''ontinue at this point
* Step 4.1 - the <code>make depend</code> step will generate a large number of warnings - these can safely be ignored

* Steps 5.8 and 5.10 - If you don't have the Net-SNMP Administration secret key (or can't remember the password!), you'll have to skip these signing steps. MD5 checksums (or full package signatures) can be generated and uploaded at a later date

== Publishing and Advertising ==

From Step 6 onwards, the process relies more on manual intervention, with relatively little being automated.
The <code>makerelease</code> script will guide you through what is required, but won't actually perform most of these actions.

* Step 6.1 - note that the example command uses Wes' SourceForge account details. Amend <code>hardaker</code> to be your SF login name.

* Step 6.2 - updating the Download web page needs to be done via the SVN repository

* Steps 6.3, 8.1, 8.4 - these attempt to open the relevant web pages for editing, but this may well fail - update the relevant pages manually (or ignore them), and '''c'''ontinue

= Producing Binaries =

== Linux RPMs ==

Creating (the traditional Net-SNMP structure) binaries for SuSE-based and RedHat-based systems
(including RHEL, Fedora and CentOS distributions) uses the RPM spec file
from <code>dist/net-snmp.spec</code>.

The procedure is as follows:
* Create <code>$HOME/rpmbuild/SPECS</code> and copy the spec file there
* Create <code>$HOME/rpmbuild/SOURCES</code> and copy the tarball there
* Ensure <code>Version</code> in the spec file matches the version of the tarball
* Append a suitable vendor identifier to the <code>Release</code> in the spec file
* Run the command <code>rpmbuild -ba $HOME/rpmbuild/SPECS/net-snmp.spec</code>

This produces three binary RPM files (under <code>$HOME/rpmbuild/RPMs</code>)
together with a source RPM file (under <code>$HOME/rpmbuild/SRPMs</code>)

(This procedure requires the RPM <code>rpm-build</code> to be installed)

== Fedora RPMs ==

Creating binaries using the RedHat structure for RPMs,
should use the RPM spec file from the Fedora repository:

* retrieve this spec file (and the accompanying files) using the command <code>git clone git://pkgs.fedoraproject.org/net-snmp</code>
* copy the file <code>net-snmp/net-snmp.spec</code> to <code>$HOME/rpmbuild/SPECS</code>
* copy the other files from the <code>net-snmp/</code> directory to <code>$HOME/rpmbuild/SOURCES</code>
* copy the tarball to <code>$HOME/rpmbuild/SOURCES</code>
* Ensure <code>Version</code> in the spec file matches the version of the tarball
* Append a suitable vendor identifier to the <code>Release</code> in the spec file
* Run the command <code>rpmbuild -ba $HOME/rpmbuild/SPECS/net-snmp.spec</code>

Note that this spec file includes RedHat-supplied patches to the code,
which may not necessarily be relevant to the version you are
working with. You may need to comment out some of the <code>PatchN</code>
definitions, and the corresponding <code>%patchN</code> setup directives.
It may also be necessary to amend the configure options used, and other
aspects of the spec file, depending on the versions involved.

An alternative build approach is to use <code>fedpkg</code>
* cd net-snmp
* Copy the tarball into the same directory
* Ensure <code>Version</code> in the file <code>net-snmp/net-snmp.spec</code> matches the version of the tarball
* Run the command <code>fedpkg local</code>

This will probabaly require the same adjustments to the spec file, as listed above.

(This procedure requires the RPMs <code>fedpkg</code> and <code>chrpath</code> to be installed)

== Linux DEBs ==

== Solaris ==

* SYSV packages
** see dist/net-snmp-solaris-build
* tar balls
** to be unpacked beneath /usr/local

== Windows ==

Release Instructions

2011-02-25T11:29:57Z

Dts12: Document possible problems arising from making two releases in succession

Release Instructions

2011-02-25T11:26:15Z

Dts12: Document problems arising from releasing from a "distclean"-ed source tree

Notes20110221

2011-02-21T20:21:52Z

Dts12:

{{meetingtime|time=20|year=2011|month=02|day=21|nextyear=2011|nextmonth=03|nextday=21|prevyear=2011|prevmonth=01|prevday=31}}

== Agenda ==

* Next Meeting
** Mar 21st has been suggested already
* Releases
** 5.5.1
*** '''5.5.1.rc1 out, 5.5.1.rc2 out later in the week'''
*** '''Unanswered: Niels' has a set of IPv6 fixes for *BSD; what should they go in?'''
** 5.3 closing?
** 5.4 pushing out another?
* Administrative
* Technical
** [[Testing]]
** [[Feature Marking and Selection]]
*** Checkin likely this week
** Windows Builds
** RPMs
** SVN vs GIT
*** slow migration proposed last time ; community split between which is better
** makerelease source has moved to [https://github.com/hardaker/makerelease github]
** 5.5.x branch architecture
* Round Table

Administrative Meetings

2011-02-21T19:52:53Z

Dts12: Point the February meeting link at the February meeting page

The Net-SNMP administrative staff holds meetings on IRC on a regular basis to discuss project issues, goals, etc. The meetings are run on the #net-snmp-admin channel. Anyone can join and participate. To add agenda items, simply add them to the list in the upcoming meetings pages. If you feel the minutes of past meetings are in error, please edit them as appropriate.

== Upcoming Meetings ==

* [[Notes20110221 | 2011-02-21]]

== Notes From Previous Meetings ==

* [[Notes20110131 | 2011-01-31]]
* [[Notes20110103 | 2011-01-03]]
* [[Notes20101129 | 2010-11-29]]
* [[Notes20101011 | 2010-10-11]]
* [[Notes20100920 | 2010-09-20]]
* [[Notes20100809 | 2010-08-09]]
* [[Notes20100607 | 2010-06-07]]
* [[Notes20100517 | 2010-05-17]]
* [[Notes20100419 | 2010-04-19]]
* [[Notes20100315 | 2010-03-15]]
* [[Notes20100222 | 2010-02-22]]
* [[Notes20100111 | 2010-01-11]]
* [[Notes20091214 | 2009-12-14]]
* [[Notes20091116 | 2009-11-16]]
* [[Notes20091012 | 2009-10-12]]
* [[Notes20090914 | 2009-09-14]]
* [[Notes20090810 | 2009-08-10]]
* [[Notes20090720 | 2009-07-20]]
* [[Notes20090615 | 2009-06-15]]
* [[Notes20090518 | 2009-05-18]]
* [[Notes20090406 | 2009-04-06]]
* [[Notes20090302 | 2009-03-02]]
* [[Notes20090202 | 2009-02-02]]
* [[Notes20090105 | 2009-01-05]]
* [[Notes20081110 | 2008-11-10]]
* [[Notes20081006 | 2008-10-06]]
* [[Notes20080915 | 2008-09-15]]
* [[Notes20080811 | 2008-08-11]]
* [[Notes20080707 | 2008-07-07]]
* [[Notes20080602 | 2008-06-02]]
* [[Notes20080509 | 2008-05-09]]
* [[Notes20080331 | 2008-03-31]]
* [[Notes20080211 | 2008-02-11]]
* [[Notes20080115 | 2008-01-15]]
* [[Notes20071211 | 2007-12-11]]
* [[Notes20071114 | 2007-11-14]]
* [[Notes20071009 | 2007-10-09]]
* [[Notes20070919 | 2007-09-19]]
* [[Notes20070823 | 2007-08-23]]
* [[Notes20070719 | 2007-07-19]]
* [[Notes20070705 | 2007-07-05]]
* [[Notes20070601 | 2007-06-01]]
* [[Notes20070511 | 2007-05-11]]
* [[Notes20070406 | 2007-04-06]]
* [[notes20070302 | 2007-03-02]]
* [[notes20070209 | 2007-02-09]]
* [[notes20061222 | 2006-12-22]]
* [[notes20061122 | 2006-11-22]]
* [[notes20061103 | 2006-11-03]]
* [[notes20060928 | 2006-09-28]]
* [[notes20060908 | 2006-09-08]]
* [[notes20060804 | 2006-08-04]]

== Future Topics ==

These items are likely topics for future discussions when time permits:

* The Great Rename (aka "svn move")
** consistent structure
** path names shorter than 100 chars to minimize tar problems
* [[Google SoC]] 2009

== Bug Bash ==

For a while, there were also separate [[BugBash]] meetings on IRC.
However these have fallen into disuse, and have not happened recently.

[[Category:Admin]]

TUT:Configuring snmptrapd

2011-01-19T12:34:10Z

Dts12: Fix generic/specific type - reported by Jacek Poplawski

[[snmptrapd]] is a Net-SNMP application that lets operators receive SNMP [[notifications]] ([[informs]] and [[traps]]) and process them.

== Configuring snmptrapd to allow traps in the door ==

By default, snmptrapd does not do anything with received notifications. You have to tell it what you want to receive notifications.

=== Configuring snmptrapd to accept SNMPv1 or SNMPv2c notifications ===

To receive SNMPv1 or SNMPv2c notifications you need to tell snmptrapd your community strings. The easiest way to do this is by using the ''authCommunity'' snmptrapd.conf configuration file token. For example, this line:

authCommunity log,execute,net public

Will let snmptrapd process notifications received using the "public" community string. Those notifications may be logged, allowed to trigger executable actions (see below), and resend data to the network (forward).

=== Configuring snmptrap to accept SNMPv3 notifications ===

SNMPv3 adds security to the SNMP protocol and is a safer way to receive notification data. But, it's a bit more complex to set up. Configuration of SNMPv3 notifications is described fully on a [[TUT:Configuring snmptrapd to receive SNMPv3 notifications|separate page]]:

== Processing Notifications ==

Generating traps is only half of the battle. We also need something
to receive the notification, and respond accordingly.
The Net-SNMP suite includes an application <code>snmptrapd</code>
which can accept and process such notifications.

By default, it will simply log all incoming notifications via syslog.
The two <code>snmptrap</code> commands described in [[TUT:snmptrap#SNMPv1_Traps]]:

$ snmptrap -v 1 -c public host '''UCD-TRAP-TEST-MIB::demotraps''' "" '''6 17''' "" \
SNMPv2-MIB::sysLocation.0 s "Just here"

and

$ snmptrap -v 2c -c public host "" '''UCD-NOTIFICATION-TEST-MIB::demoNotif''' \
SNMPv2-MIB::sysLocation.0 s "Just here"

would be logged as:

1999-11-12 23:26:07 localhost [127.0.0.1] UCD-TRAP-TEST-MIB::demotraps:
Enterprise Specific Trap (demoTrap) Uptime: 1 day, 5:34:06
SNMPv2-MIB::sysLocation.0 = "Just here"

and

1999-11-13 08:31:33 localhost [127.0.0.1]:
SNMPv2-MIB::sysUpTime.0 = Timeticks: (13917129) 1 day, 14:39:31.29
SNMPv2-MIB::snmpTrapOID.0 = OID: UCD-NOTIFICATION-TEST-MIB::demoNotif
SNMPv2-MIB::sysLocation.0 = "just here"

respectively (MIB is defined in [[TUT:snmptrap#Trap_Definitions]]).

=== Trap Handlers ===

The snmptrapd utility also has the ability to execute other programs on the reception
of a trap. This is controlled by the traphandle directive, with the syntax

traphandle OID command

Notice, that this only takes an OID to determine which trap (or notification) is received. This means that SNMPv1 traps, which have a ''trap type'' and ''specific type'', need to be represented in SNMPv2 format, which is described in RFC 2089.

==== Matching SNMPv1 OIDs ====
SNMPv1 traps fall into two broad categories: ''generic'' and ''enterprise specific''. Generic traps use ''trap types'' 0 through 5, and do not use the ''specific type''. To match a generic trap, the traphandle OID should be the SNMPv2-MIB::snmpTraps OID, with an additional final OID of the ''trap type'' + 1. For example, to match linkDown traps (''trap type'' 2), the correct OID would be "1.3.6.1.6.3.1.1.5.3" (or SNMPv2-MIB::snmpTraps.3, which is also IF-MIB::linkDown).

''SNMPv2-MIB::snmpTraps 1.3.6.1.6.3.1.1.5''
SNMPv2-MIB::coldStart 1.3.6.1.6.3.1.1.5.'''1'''
SNMPv2-MIB::warmStart 1.3.6.1.6.3.1.1.5.'''2'''
IF-MIB::linkDown 1.3.6.1.6.3.1.1.5.'''3'''
IF-MIB::linkUp 1.3.6.1.6.3.1.1.5.'''4'''
SNMPv2-MIB::authenticationFailure 1.3.6.1.6.3.1.1.5.'''5'''

When the ''trap type'' is 6, the trap is an ''enterprise specific'' trap. When matching these traps, the traphandle OID is constructed using the enterprise OID and ''specific type'' specified in the trap. Earlier in the tutorial, we sent a SNMPv1 enterprise specific trap with an enterprise OID of UCD-TRAP-TEST-MIB::demotraps, a ''trap type'' of 6 and a ''specific type'' of 17. To match this trap type, the traphandle OID should be the enterprise OID, plus 0, plus the ''specific type''. So the correct OID would be ".1.3.6.1.4.1.2021.13.990.0.17" (or UCD-TRAP-TEST-MIB::demoTrap).

==== Matching SNMPv2 OIDs ====
SNMPv2 traps and informs are much easier, because they include the correct OID in the SNMPv2-MIB::snmpTrapOID.0 variable in the trap.

==== Example handler script ====
The command specifies a command to be executed by snmptrapd upon reception by the command. This command is executed with the data of the trap as its standard input. The first line is the host name, the second the IP address of the trap sender, and the following lines consists of an OID VALUE pair with the data from the received trap.

A simple shell script to be called from snmptrapd is the following:

#!/bin/sh

read host
read ip
vars=

while read oid val
do
if [ "$vars" = "" ]
then
vars="$oid = $val"
else
vars="$vars, $oid = $val"
fi
done

echo trap: $1 $host $ip $vars

Now, given the following sample snmptrapd.conf file,

# the generic traps
traphandle SNMPv2-MIB::coldStart /home/nba/bin/traps cold
traphandle SNMPv2-MIB::warmStart /home/nba/bin/traps warm
traphandle IF-MIB::linkDown /home/nba/bin/traps down
traphandle IF-MIB::linkUp /home/nba/bin/traps up
traphandle SNMPv2-MIB::authenticationFailure /home/nba/bin/traps auth
# this one is deprecated
traphandle .1.3.6.1.6.3.1.1.5.6 /home/nba/bin/traps egp-neighbor-loss

# enterprise specific traps
traphandle UCD-TRAP-TEST-MIB::demoTrap /home/nba/bin/traps demo-trap
traphandle UCD-NOTIFICATION-TEST-MIB::demoNotif /home/nba/bin/traps demo-notif

The following snmptrap invocation, to issue a generic Link down trap (OID 1.3.6.1.6.3.1.1.5.'''3'''),

% ''snmptrap -v 1 -c public localhost TRAP-TEST-MIB::demotraps localhost '''2''' 0 "" \
IF-MIB::ifIndex i 1''

results in the following output from snmptrapd:

1999-11-13 12:46:49 localhost [127.0.0.1] TRAP-TEST-MIB::traps:
Link Down Trap (0) Uptime: 1 day, 18:54:46.27
IF-MIB::ifIndex.0 = 1

and the following output from the handler:

trap: down localhost 127.0.0.1 SNMPv2-MIB::sysUpTime = 1:18:54:46.27, SNMPv2-MIB::snmpTrapOID = IF-MIB::linkDown, IF-MIB::ifIndex.0 = 1, SNMPv2-MIB::snmpTrapEnterprise = TRAP-TEST-MIB::traps

and issuing our enterprise specific trap ('''.1.3.6.1.4.1.2021.13.990.0.17''') gives this output from our handler:

trap: demoTrap localhost 127.0.0.1 SNMPv2-MIB::sysUpTime = 1:19:00:48.01, SNMPv2-MIB::snmpTrapOID = '''UCD-TRAP-TEST-MIB::demoTrap''', SNMPv2-MIB::sysLocation.0 = "just here", SNMPv2-MIB::snmpTrapEnterprise = UCD-TRAP-TEST-MIB::traps

and finally our enterprise specific notification:

trap: demoNotif localhost 127.0.0.1 SNMPv2-MIB::sysUpTime.0 = 1:19:02:06.33, SNMPv2-MIB::snmpTrapOID.0 = UCD-NOTIFICATION-TEST-MIB::demoNotif, SNMPv2-MIB::sysLocation.0 = "just here"

<hr>

{{TUT:LIST}}

Release Instructions

2011-01-13T16:17:15Z

Dts12: Document experiences in rolling out a release

Release Instructions

2011-01-13T13:49:07Z

Dts12: Installing MakeRelease

Build System

2011-01-06T08:44:22Z

Dts12: Link to binary release instructions

[[Category: Admin]]

== For Users ==

=== Unix ===

./configure [options, see "configure --help" for a list]
make
make test
su
make install

The same procedure applies to builds with Cygwin on Windows. 
See [http://www.net-snmp.org/docs/readmefiles.html README.*] for important notes for particular platforms.

=== Windows ===

There are several ways to build on Windows:

* MS Visual C++
* MinGW / MSYS
* Cygwin (see "Unix" above)

See [[Build_System/Windows]] for the status of compiling with the various Windows environments.

See [[Build_System/Windows_features]] for a comparison of the features implemented in each of the Windows build environments.

See [http://www.net-snmp.org/docs/README.win32.html README.win32] for further details.

== For Coders ==

See [[Release_Instructions]] for information about building binary packages on various systems.

=== Tool Versions ===

{|
! Versions !! Autoconf !! Automake !! Libtool
|-
| Trunk ''(5.7-to-be)''
| autoconf [ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.68.tar.bz2 2.68]
| automake [ftp://ftp.gnu.org/gnu/automake/automake-1.11.tar.bz2 1.11]
| libtool [ftp://ftp.gnu.org/gnu/libtool/libtool-2.4.tar.gz 2.4 + patch (see below)]

|-
| 5.6
| autoconf [ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.63.tar.bz2 2.63]
| automake [ftp://ftp.gnu.org/gnu/automake/automake-1.11.tar.bz2 1.11]
| libtool [ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6a.tar.gz 2.2.6a]

|-
| 5.5
| autoconf [ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.63.tar.bz2 2.63]
| automake [ftp://ftp.gnu.org/gnu/automake/automake-1.10.1.tar.bz2 1.10.1]
| libtool [ftp://ftp.gnu.org/gnu/libtool/libtool-2.2.6a.tar.gz 2.2.6a]

|-
| 5.4.2+
| autoconf [ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.59.tar.bz2 2.59]
| automake [ftp://ftp.gnu.org/gnu/automake/automake-1.10.1.tar.bz2 1.10.1]
| libtool [ftp://ftp.gnu.org/gnu/libtool/libtool-1.5.26.tar.gz 1.5.26]

|-
| 5.4/5.4.1
| autoconf [ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.59.tar.bz2 2.59]
| automake (which version ?)
| libtool [ftp://ftp.gnu.org/gnu/libtool/libtool-1.5.24.tar.gz 1.5.24]

|-
| earlier
| autoconf [ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.59.tar.bz2 2.59]
| automake (which version ?)
| libtool [ftp://ftp.gnu.org/gnu/libtool/libtool-1.4.3.tar.gz 1.4.3]
|}

=== Files ===

* configure: auto-generated by autoconf from configure.in and acinclude.m4 (branches) or configure.ac, configure.d/* and m4/* (trunk)
* configure.in (5.4.x and earlier) or configure.ac and configure.d/* (trunk): major source file to implement configure magic. ''Run autoconf and autoheader after any change. New definitions may need to be copied to win32/net-snmp/net-snmp-config.h[.in].''
* acconfig.h: autoconf variable definitions, descriptions and default values. Deprecated (for new definitions) in favor of AC_DEFINE() in configure.in / configure.d/*. ''Run autoheader after any change. New definitions may need to be copied to win32/net-snmp/net-snmp-config.h[.in].''
* acinclude.m4 (branches) or m4/ac* and m4/netsnmp* (trunk): Net-SNMP specific autoconf macros. ''Run autoconf after any change.''
* include/net-snmp/net-snmp-config.h: auto-generated by autoheader from configure.in/configure.ac and acconfig.h
* ltmain.sh: copied from libtool (created/updated by libtoolize --copy --force)
* aclocal.m4: contains includes of all used files in m4/*(created/updated by aclocal)
* config.guess, config.sub: platform detection shell script (created/updated by libtoolize --copy --force; from GNU config project)
* win32/net-snmp/net-snmp-config.h.in: used by win32/Configure to create win32/net-snmp/net-snmp-config.h
* win32/net-snmp/net-snmp-config.h: definitions for Win32 (non-Cygwin) builds
* win32/lib*/lib*.def: public/exported symbols/functions from Net-SNMP libraries for Win32 builds. ''If you introduce new public functions, please also add them here!''
* Makefile.in (also in most sub-directories): source for Makefile (the latter being generated by configure by substituting autoconf definitions and concatenating with Makefile.top and Makefile.rules)
* net-snmp-config.in: source for net-snmp-config (the latter being generated by configure)
* sedscript.in: source for sedscript (the latter being generated by configure)

=== Updating ===
Assuming that you have changed any of the above and have the right tool versions installed - in order to update all the generated files you can do either
aclocal -I m4
libtoolize --copy
autoconf
autoheader
or
autoreconf -i
but in the later case you must make sure that the tool versions that autoreconf calls are the correct ones.

=== Patches ===
When using libtool 2.4, you will need the following patch (see also [http://blog.gmane.org/gmane.comp.gnu.libtool.bugs/month=20100601]):
<pre>
diff -u -r orig/libtool-2.4/libltdl/config/ltmain.m4sh libtool-2.4/libltdl/config/ltmain.m4sh
--- orig/libtool-2.4/libltdl/config/ltmain.m4sh 2010-09-22 16:45:18.000000000 +0200
+++ libtool-2.4/libltdl/config/ltmain.m4sh 2010-10-22 08:30:21.000000000 +0200
@@ -5045,13 +5045,14 @@
# -m*, -t[45]*, -txscale* architecture-specific flags for GCC
# -F/path path to uninstalled frameworks, gcc on darwin
# -p, -pg, --coverage, -fprofile-* profiling flags for GCC
+ # -fstack-protector* stack protector flags for GCC
# @file GCC response files
# -tp=* Portland pgcc target processor selection
# --sysroot=* for sysroot support
# -O*, -flto*, -fwhopr*, -fuse-linker-plugin GCC link-time optimization
-64|-mips[0-9]|-r[0-9][0-9]*|-xarch=*|-xtarget=*|+DA*|+DD*|-q*|-m*| \
-t[45]*|-txscale*|-p|-pg|--coverage|-fprofile-*|-F*|@*|-tp=*|--sysroot=*| \
- -O*|-flto*|-fwhopr*|-fuse-linker-plugin)
+ -O*|-flto*|-fwhopr*|-fuse-linker-plugin|-fstack-protector*)
func_quote_for_eval "$arg"
arg="$func_quote_for_eval_result"
func_append compile_command " $arg"
diff -u -r orig/libtool-2.4/libltdl/config/ltmain.sh libtool-2.4/libltdl/config/ltmain.sh
--- orig/libtool-2.4/libltdl/config/ltmain.sh 2010-09-22 16:45:43.000000000 +0200
+++ libtool-2.4/libltdl/config/ltmain.sh 2010-10-22 08:37:07.000000000 +0200
@@ -5834,13 +5834,14 @@
# -m*, -t[45]*, -txscale* architecture-specific flags for GCC
# -F/path path to uninstalled frameworks, gcc on darwin
# -p, -pg, --coverage, -fprofile-* profiling flags for GCC
+ # -fstack-protector* stack protector flags for GCC
# @file GCC response files
# -tp=* Portland pgcc target processor selection
# --sysroot=* for sysroot support
# -O*, -flto*, -fwhopr*, -fuse-linker-plugin GCC link-time optimization
-64|-mips[0-9]|-r[0-9][0-9]*|-xarch=*|-xtarget=*|+DA*|+DD*|-q*|-m*| \
-t[45]*|-txscale*|-p|-pg|--coverage|-fprofile-*|-F*|@*|-tp=*|--sysroot=*| \
- -O*|-flto*|-fwhopr*|-fuse-linker-plugin)
+ -O*|-flto*|-fwhopr*|-fuse-linker-plugin|-fstack-protector*)
func_quote_for_eval "$arg"
arg="$func_quote_for_eval_result"
func_append compile_command " $arg"
</pre>

Release Instructions

2011-01-06T08:42:40Z

Dts12: Fuller description of generating Linux RPMs

This page documents varios aspects of creating releases and binary builds suitable for distribution of the project products:

= Releasing Source Code =

The current release procedures are reliant on the [[makerelease]] system

...

= Producing Binaries =

== Linux RPMs ==

Creating binaries for SuSE-based and RedHat-based systems
(including RHEL, Fedora and CentOS distributions) uses the RPM spec file
from <code>dist/net-snmp.spec</code>.

The procedure is as follows:
* Create <code>$HOME/rpmbuild/SPECS</code> and copy the spec file there
* Create <code>$HOME/rpmbuild/SOURCES</code> and copy the tarball there
* Ensure <code>Version</code> in the spec file matches the version of the tarball
* Append a suitable vendor identifier to the <code>Release</code> in the spec file
* Run the command <code>rpmbuild -ba $HOME/rpmbuild/SPECS/net-snmp.spec</code>

This produces three binary RPM files (under <code>$HOME/rpmbuild/RPMs</code>)
together with a source RPM file (under <code>$HOME/rpmbuild/SRPMs</code>)

== Linux DEBs ==

== Solaris ==

* SYSV packages
** see dist/net-snmp-solaris-build
* tar balls
** to be unpacked beneath /usr/local

== Windows ==

Notes20110103

2010-12-22T22:05:01Z

Dts12:

{{meetingtime|time=20|year=2011|month=01|day=03|nextyear=2011|nextmonth=02|nextday=??|prevyear=2010|prevmonth=11|prevday=29}}

== Agenda ==

* Next Meeting
* Releases
** 5.6.1
** 5.5.1
** others
* Administrative
** Release Policy - is RC "show-stopper" threshold still appropriate
* Technical
* Round Table

Administrative Meetings

2010-12-22T22:02:17Z

Dts12: Pension off BugBash

The Net-SNMP administrative staff holds meetings on IRC on a regular basis to discuss project issues, goals, etc. The meetings are run on the #net-snmp-admin channel. Anyone can join and participate. To add agenda items, simply add them to the list in the upcoming meetings pages. If you feel the minutes of past meetings are in error, please edit them as appropriate.

== Upcoming Meetings ==

* [[Notes20110103 | 2011-01-03]]

== Notes From Previous Meetings ==

* [[Notes20101129 | 2010-11-29]]
* [[Notes20101011 | 2010-10-11]]
* [[Notes20100920 | 2010-09-20]]
* [[Notes20100809 | 2010-08-09]]
* [[Notes20100607 | 2010-06-07]]
* [[Notes20100517 | 2010-05-17]]
* [[Notes20100419 | 2010-04-19]]
* [[Notes20100315 | 2010-03-15]]
* [[Notes20100222 | 2010-02-22]]
* [[Notes20100111 | 2010-01-11]]
* [[Notes20091214 | 2009-12-14]]
* [[Notes20091116 | 2009-11-16]]
* [[Notes20091012 | 2009-10-12]]
* [[Notes20090914 | 2009-09-14]]
* [[Notes20090810 | 2009-08-10]]
* [[Notes20090720 | 2009-07-20]]
* [[Notes20090615 | 2009-06-15]]
* [[Notes20090518 | 2009-05-18]]
* [[Notes20090406 | 2009-04-06]]
* [[Notes20090302 | 2009-03-02]]
* [[Notes20090202 | 2009-02-02]]
* [[Notes20090105 | 2009-01-05]]
* [[Notes20081110 | 2008-11-10]]
* [[Notes20081006 | 2008-10-06]]
* [[Notes20080915 | 2008-09-15]]
* [[Notes20080811 | 2008-08-11]]
* [[Notes20080707 | 2008-07-07]]
* [[Notes20080602 | 2008-06-02]]
* [[Notes20080509 | 2008-05-09]]
* [[Notes20080331 | 2008-03-31]]
* [[Notes20080211 | 2008-02-11]]
* [[Notes20080115 | 2008-01-15]]
* [[Notes20071211 | 2007-12-11]]
* [[Notes20071114 | 2007-11-14]]
* [[Notes20071009 | 2007-10-09]]
* [[Notes20070919 | 2007-09-19]]
* [[Notes20070823 | 2007-08-23]]
* [[Notes20070719 | 2007-07-19]]
* [[Notes20070705 | 2007-07-05]]
* [[Notes20070601 | 2007-06-01]]
* [[Notes20070511 | 2007-05-11]]
* [[Notes20070406 | 2007-04-06]]
* [[notes20070302 | 2007-03-02]]
* [[notes20070209 | 2007-02-09]]
* [[notes20061222 | 2006-12-22]]
* [[notes20061122 | 2006-11-22]]
* [[notes20061103 | 2006-11-03]]
* [[notes20060928 | 2006-09-28]]
* [[notes20060908 | 2006-09-08]]
* [[notes20060804 | 2006-08-04]]

== Future Topics ==

These items are likely topics for future discussions when time permits:

* The Great Rename (aka "svn move")
** consistent structure
** path names shorter than 100 chars to minimize tar problems
* [[Google SoC]] 2009

== Bug Bash ==

For a while, there were also separate [[BugBash]] meetings on IRC.
However these have fallen into disuse, and have not happened recently.

[[Category:Admin]]

Administrative Meetings

2010-12-22T22:00:38Z

Dts12: Link for January meeting

The Net-SNMP administrative staff holds meetings on IRC on a regular basis to discuss project issues, goals, etc. The meetings are run on the #net-snmp-admin channel. Anyone can join and participate. To add agenda items, simply add them to the list in the upcoming meetings pages. If you feel the minutes of past meetings are in error, please edit them as appropriate.

== Upcoming Meetings ==

* [[Notes20110103 | 2011-01-03]]

== Notes From Previous Meetings ==

* [[Notes20101129 | 2010-11-29]]
* [[Notes20101011 | 2010-10-11]]
* [[Notes20100920 | 2010-09-20]]
* [[Notes20100809 | 2010-08-09]]
* [[Notes20100607 | 2010-06-07]]
* [[Notes20100517 | 2010-05-17]]
* [[Notes20100419 | 2010-04-19]]
* [[Notes20100315 | 2010-03-15]]
* [[Notes20100222 | 2010-02-22]]
* [[Notes20100111 | 2010-01-11]]
* [[Notes20091214 | 2009-12-14]]
* [[Notes20091116 | 2009-11-16]]
* [[Notes20091012 | 2009-10-12]]
* [[Notes20090914 | 2009-09-14]]
* [[Notes20090810 | 2009-08-10]]
* [[Notes20090720 | 2009-07-20]]
* [[Notes20090615 | 2009-06-15]]
* [[Notes20090518 | 2009-05-18]]
* [[Notes20090406 | 2009-04-06]]
* [[Notes20090302 | 2009-03-02]]
* [[Notes20090202 | 2009-02-02]]
* [[Notes20090105 | 2009-01-05]]
* [[Notes20081110 | 2008-11-10]]
* [[Notes20081006 | 2008-10-06]]
* [[Notes20080915 | 2008-09-15]]
* [[Notes20080811 | 2008-08-11]]
* [[Notes20080707 | 2008-07-07]]
* [[Notes20080602 | 2008-06-02]]
* [[Notes20080509 | 2008-05-09]]
* [[Notes20080331 | 2008-03-31]]
* [[Notes20080211 | 2008-02-11]]
* [[Notes20080115 | 2008-01-15]]
* [[Notes20071211 | 2007-12-11]]
* [[Notes20071114 | 2007-11-14]]
* [[Notes20071009 | 2007-10-09]]
* [[Notes20070919 | 2007-09-19]]
* [[Notes20070823 | 2007-08-23]]
* [[Notes20070719 | 2007-07-19]]
* [[Notes20070705 | 2007-07-05]]
* [[Notes20070601 | 2007-06-01]]
* [[Notes20070511 | 2007-05-11]]
* [[Notes20070406 | 2007-04-06]]
* [[notes20070302 | 2007-03-02]]
* [[notes20070209 | 2007-02-09]]
* [[notes20061222 | 2006-12-22]]
* [[notes20061122 | 2006-11-22]]
* [[notes20061103 | 2006-11-03]]
* [[notes20060928 | 2006-09-28]]
* [[notes20060908 | 2006-09-08]]
* [[notes20060804 | 2006-08-04]]

== Future Topics ==

These items are likely topics for future discussions when time permits:

* The Great Rename (aka "svn move")
** consistent structure
** path names shorter than 100 chars to minimize tar problems
* [[Google SoC]] 2009

== Bug Bash ==

There are also separate [[BugBash]] meetings on IRC.

[[Category:Admin]]

Notes20110103

2010-12-22T21:58:07Z

Dts12: Bare Agenda

Notes20101129

2010-12-22T21:57:47Z

Dts12: Fix link for next meeting

{{meetingtime|time=20|year=2010|month=11|day=29|nextyear=2011|nextmonth=01|nextday=03|prevyear=2010|prevmonth=10|prevday=11}}

== Agenda ==

* Next Meeting
** Jan 3rd
* Releases
** 5.6.1 (starting today)
*** '''short 1-week turn around times'''
** 5.5.1 (aim for Jan)
*** '''will start .pre1 a week or two after 5.6.1.pre1'''
** 5.3.4 (post 5.5.1)
* Administrative
** Policy reminder on changes [[Notes20101011|from last meeting]]
** Patch applying pain during a release?
*** cross release patches should be applied at the same time/revision, ideally
*** release on one branch breaks this (or delays applying stuff)
*** Results:
***# Live with it
***# use more branches (create a new branch just for the release, off the existing -patches branch)
*** '''Live with it'''
** IETF Report
*** KSM is probably going to resurface; hopefully with code contributions
*** power management is doing a lot of work too
* Technical
** Unit tests
*** Wes got trounced in the last month and didn't write the promised documentation
*** '''bvassche has been creating lots of tests'''
*** '''tabled until next time when Wes can get docs written'''
** autoconf vs the world
*** ''still no takers on doing the work''
** stream lined/stripped-down
*** work under way to make a "read only" code set using an ifdefs (along with a script to actually remove it as well)
*** thinking about multi-pass compile for really-reduced code. Something like sample at bottom.
*** '''discussion results captured below'''
* Round Table
** dts12: upcoming releases
** Wes: most of the above discussion items
** rstory: dtls testing

=== feature possibility thinking ===

Marking of features. Standard configure/make would always produce 1 for these ifdefs

// will only compile if needed by something else
NETSNMP_BEGIN_FEATURE(counter64)
... code ...
NETSNMP_END_FEATURE(counter64)

// something else says it's needed
NETSNMP_REQUIRE_FEATURE(counter64)

Adding an extra "make reduce" or something would turn them into real ifdefs

.

==== resulting conclusions ====

# ifdefs over macros
#* but simple ifdefs. #ifdef NETSNMP_IMPLEMENTS_FEATURE
# by default called from configure
#* but actually runs a sub-script for non-configure-possible platforms
# new parallel to config_require
#* start with something new
#* maybe convert the MIB config_require later if possible
# defaults to including all features
# will be useful for reducing backwards-compatability code

Notes20101129

2010-11-02T14:13:44Z

Dts12: Bring upcoming releases into line with agreed plan

{{meetingtime|time=20|year=2010|month=11|day=29|nextyear=2010|nextmonth=12|nextday=??|prevyear=2010|prevmonth=10|prevday=11}}

== Agenda ==

* Next Meeting
* Releases
** 5.6.1
** 5.5.1 (aim for Jan)
** 5.3.4 (post 5.5.1)
*

Administrative Meetings

2010-11-02T14:10:58Z

Dts12: November 2010 meeting

The Net-SNMP administrative staff holds meetings on IRC on a regular basis to discuss project issues, goals, etc. The meetings are run on the #net-snmp-admin channel. Anyone can join and participate. To add agenda items, simply add them to the list in the upcoming meetings pages. If you feel the minutes of past meetings are in error, please edit them as appropriate.

== Upcoming Meetings ==

* [[Notes20101129 | 2010-11-29]]

== Notes From Previous Meetings ==

* [[Notes20101011 | 2010-10-11]]
* [[Notes20100920 | 2010-09-20]]
* [[Notes20100809 | 2010-08-09]]
* [[Notes20100607 | 2010-06-07]]
* [[Notes20100517 | 2010-05-17]]
* [[Notes20100419 | 2010-04-19]]
* [[Notes20100315 | 2010-03-15]]
* [[Notes20100222 | 2010-02-22]]
* [[Notes20100111 | 2010-01-11]]
* [[Notes20091214 | 2009-12-14]]
* [[Notes20091116 | 2009-11-16]]
* [[Notes20091012 | 2009-10-12]]
* [[Notes20090914 | 2009-09-14]]
* [[Notes20090810 | 2009-08-10]]
* [[Notes20090720 | 2009-07-20]]
* [[Notes20090615 | 2009-06-15]]
* [[Notes20090518 | 2009-05-18]]
* [[Notes20090406 | 2009-04-06]]
* [[Notes20090302 | 2009-03-02]]
* [[Notes20090202 | 2009-02-02]]
* [[Notes20090105 | 2009-01-05]]
* [[Notes20081110 | 2008-11-10]]
* [[Notes20081006 | 2008-10-06]]
* [[Notes20080915 | 2008-09-15]]
* [[Notes20080811 | 2008-08-11]]
* [[Notes20080707 | 2008-07-07]]
* [[Notes20080602 | 2008-06-02]]
* [[Notes20080509 | 2008-05-09]]
* [[Notes20080331 | 2008-03-31]]
* [[Notes20080211 | 2008-02-11]]
* [[Notes20080115 | 2008-01-15]]
* [[Notes20071211 | 2007-12-11]]
* [[Notes20071114 | 2007-11-14]]
* [[Notes20071009 | 2007-10-09]]
* [[Notes20070919 | 2007-09-19]]
* [[Notes20070823 | 2007-08-23]]
* [[Notes20070719 | 2007-07-19]]
* [[Notes20070705 | 2007-07-05]]
* [[Notes20070601 | 2007-06-01]]
* [[Notes20070511 | 2007-05-11]]
* [[Notes20070406 | 2007-04-06]]
* [[notes20070302 | 2007-03-02]]
* [[notes20070209 | 2007-02-09]]
* [[notes20061222 | 2006-12-22]]
* [[notes20061122 | 2006-11-22]]
* [[notes20061103 | 2006-11-03]]
* [[notes20060928 | 2006-09-28]]
* [[notes20060908 | 2006-09-08]]
* [[notes20060804 | 2006-08-04]]

== Future Topics ==

These items are likely topics for future discussions when time permits:

* The Great Rename (aka "svn move")
** consistent structure
** path names shorter than 100 chars to minimize tar problems
* [[Google SoC]] 2009

== Bug Bash ==

There are also separate [[BugBash]] meetings on IRC.

[[Category:Admin]]

Notes20101129

2010-11-02T14:10:01Z

Dts12: Fix year in DST warning

Build System

2010-10-21T14:30:48Z

Dts12: Tabulate the autoconf/libtool version information

Notes20101011

2010-10-06T13:52:54Z

Dts12:

{{meetingtime|time=19|year=2010|month=10|day=11|nextyear=2010|nextmonth=11|nextday=??|prevyear=2010|prevmonth=09|prevday=20}}

== Agenda ==

* Next Meeting Date
* Releases
** 5.6
*** Upload permissions
*** Binary Release instructions (http://www.net-snmp.org/wiki/index.php/Release_Instructions)
*** Binary Release MIB modules (e.g. examples)
** Next branch to target?
** Release Policy (http://www.net-snmp.org/dev/release-policy.html)
* Administrative
* Technical
** Future and continual discussion topics
*** testing infrastructure and unit tests
*** build cmake vs ??
*** streamlined/stripped-down library and agent
* Round Table

Administrative Meetings

2010-08-09T21:48:18Z

Dts12:

The Net-SNMP administrative staff holds meetings on IRC on a regular basis to discuss project issues, goals, etc. The meetings are run on the #net-snmp-admin channel. Anyone can join and participate. To add agenda items, simply add them to the list in the upcoming meetings pages. If you feel the minutes of past meetings are in error, please edit them as appropriate.

== Upcoming Meetings ==

* [[Notes20100913 | 2010-09-13]]

== Notes From Previous Meetings ==

* [[Notes20100809 | 2010-08-09]]
* [[Notes20100607 | 2010-06-07]]
* [[Notes20100517 | 2010-05-17]]
* [[Notes20100419 | 2010-04-19]]
* [[Notes20100315 | 2010-03-15]]
* [[Notes20100222 | 2010-02-22]]
* [[Notes20100111 | 2010-01-11]]
* [[Notes20091214 | 2009-12-14]]
* [[Notes20091116 | 2009-11-16]]
* [[Notes20091012 | 2009-10-12]]
* [[Notes20090914 | 2009-09-14]]
* [[Notes20090810 | 2009-08-10]]
* [[Notes20090720 | 2009-07-20]]
* [[Notes20090615 | 2009-06-15]]
* [[Notes20090518 | 2009-05-18]]
* [[Notes20090406 | 2009-04-06]]
* [[Notes20090302 | 2009-03-02]]
* [[Notes20090202 | 2009-02-02]]
* [[Notes20090105 | 2009-01-05]]
* [[Notes20081110 | 2008-11-10]]
* [[Notes20081006 | 2008-10-06]]
* [[Notes20080915 | 2008-09-15]]
* [[Notes20080811 | 2008-08-11]]
* [[Notes20080707 | 2008-07-07]]
* [[Notes20080602 | 2008-06-02]]
* [[Notes20080509 | 2008-05-09]]
* [[Notes20080331 | 2008-03-31]]
* [[Notes20080211 | 2008-02-11]]
* [[Notes20080115 | 2008-01-15]]
* [[Notes20071211 | 2007-12-11]]
* [[Notes20071114 | 2007-11-14]]
* [[Notes20071009 | 2007-10-09]]
* [[Notes20070919 | 2007-09-19]]
* [[Notes20070823 | 2007-08-23]]
* [[Notes20070719 | 2007-07-19]]
* [[Notes20070705 | 2007-07-05]]
* [[Notes20070601 | 2007-06-01]]
* [[Notes20070511 | 2007-05-11]]
* [[Notes20070406 | 2007-04-06]]
* [[notes20070302 | 2007-03-02]]
* [[notes20070209 | 2007-02-09]]
* [[notes20061222 | 2006-12-22]]
* [[notes20061122 | 2006-11-22]]
* [[notes20061103 | 2006-11-03]]
* [[notes20060928 | 2006-09-28]]
* [[notes20060908 | 2006-09-08]]
* [[notes20060804 | 2006-08-04]]

== Future Topics ==

These items are likely topics for future discussions when time permits:

* The Great Rename (aka "svn move")
** consistent structure
** path names shorter than 100 chars to minimize tar problems
* [[Google SoC]] 2009

== Bug Bash ==

There are also separate [[BugBash]] meetings on IRC.

[[Category:Admin]]

Notes20100809

2010-08-09T21:47:26Z

Dts12: Minutes of the meeting

{{meetingtime|time=20|year=2010|month=08|day=09|nextyear=2010|nextmonth=09|nextday=13|prevyear=2010|prevmonth=06|prevday=07}}

== Agenda ==

* Next Meeting Date
** '''Sept 13th'''
* Releases
** 5.6
*** '''Ready to move to RC1''' (?Friday)
** [http://www.mail-archive.com/net-snmp-coders@lists.sourceforge.net/msg15837.html mib2c guidance]
*** '''Discussion over appropriate guidance to those choosing which table framework to use'''
**** ''DTS to post proposed template on mailing list, for discussion/dissection''
*** '''Should table templates include cache support by default''' - ''prompt the user''
** man pages
*** '''Should doxygen output be man pages or (just) HTML'''
**** ''Suppress "non-useful" man pages - look at others''
* Administrative
** ''none''
* Technical
** ''none''
* Round Table

Administrative Meetings

2010-08-09T11:26:03Z

Dts12: Change of date for next meeting

The Net-SNMP administrative staff holds meetings on IRC on a regular basis to discuss project issues, goals, etc. The meetings are run on the #net-snmp-admin channel. Anyone can join and participate. To add agenda items, simply add them to the list in the upcoming meetings pages. If you feel the minutes of past meetings are in error, please edit them as appropriate.

== Upcoming Meetings ==

* [[Notes20100809 | 2010-08-09]]

== Notes From Previous Meetings ==

* [[Notes20100607 | 2010-06-07]]
* [[Notes20100517 | 2010-05-17]]
* [[Notes20100419 | 2010-04-19]]
* [[Notes20100315 | 2010-03-15]]
* [[Notes20100222 | 2010-02-22]]
* [[Notes20100111 | 2010-01-11]]
* [[Notes20091214 | 2009-12-14]]
* [[Notes20091116 | 2009-11-16]]
* [[Notes20091012 | 2009-10-12]]
* [[Notes20090914 | 2009-09-14]]
* [[Notes20090810 | 2009-08-10]]
* [[Notes20090720 | 2009-07-20]]
* [[Notes20090615 | 2009-06-15]]
* [[Notes20090518 | 2009-05-18]]
* [[Notes20090406 | 2009-04-06]]
* [[Notes20090302 | 2009-03-02]]
* [[Notes20090202 | 2009-02-02]]
* [[Notes20090105 | 2009-01-05]]
* [[Notes20081110 | 2008-11-10]]
* [[Notes20081006 | 2008-10-06]]
* [[Notes20080915 | 2008-09-15]]
* [[Notes20080811 | 2008-08-11]]
* [[Notes20080707 | 2008-07-07]]
* [[Notes20080602 | 2008-06-02]]
* [[Notes20080509 | 2008-05-09]]
* [[Notes20080331 | 2008-03-31]]
* [[Notes20080211 | 2008-02-11]]
* [[Notes20080115 | 2008-01-15]]
* [[Notes20071211 | 2007-12-11]]
* [[Notes20071114 | 2007-11-14]]
* [[Notes20071009 | 2007-10-09]]
* [[Notes20070919 | 2007-09-19]]
* [[Notes20070823 | 2007-08-23]]
* [[Notes20070719 | 2007-07-19]]
* [[Notes20070705 | 2007-07-05]]
* [[Notes20070601 | 2007-06-01]]
* [[Notes20070511 | 2007-05-11]]
* [[Notes20070406 | 2007-04-06]]
* [[notes20070302 | 2007-03-02]]
* [[notes20070209 | 2007-02-09]]
* [[notes20061222 | 2006-12-22]]
* [[notes20061122 | 2006-11-22]]
* [[notes20061103 | 2006-11-03]]
* [[notes20060928 | 2006-09-28]]
* [[notes20060908 | 2006-09-08]]
* [[notes20060804 | 2006-08-04]]

== Future Topics ==

These items are likely topics for future discussions when time permits:

* The Great Rename (aka "svn move")
** consistent structure
** path names shorter than 100 chars to minimize tar problems
* [[Google SoC]] 2009

== Bug Bash ==

There are also separate [[BugBash]] meetings on IRC.

[[Category:Admin]]