Provided by: tinysnmp-agent_0.8.5_i386


        tinysnmp.conf - TinySNMPd(8) configuration file


        The  TinySNMP agent configuration file consist of a list of Cisco-style
        statements, but may also contain bash-style (hash) comments and whites‐
        pace which are simply ignored.


        User name or uid of user as which to run the agent.
               user ( <userid> | <username> )
        Group name or gid of group as which to run agent.
               group ( <groupid> | <groupname> )
        The  file  in  which the agent should record its process identification
        number when it starts. This file  is  only  created  if  the  agent  is
        started as a daemon.
               pidfile <filename>
        Address  which  the  server binds to. Only connections arriving at this
        address will be accepted.
               listen ( <hostname> | <address> ) [ : ( <service> | <port> ) ]
        Hosts/subnets allowed access to the agent. There may be multiple  allow
               allow ( <hostname> | <address> | <network> [ / <cidr-mask> ] )
        Community string which clients must use to connect to the server.
               community <community-string>
        Number of seconds to cache ObjectID’s between snmp module updates. This
        statement is optional and if omittted, relevant module update callbacks
        will be called every time a request is made.  You shouldn’t need to ask
        questions about the configuration file, because the configuration  file
        for TinySNMPd is well commented by default.
               cache <timeout-in-seconds>
        Some  mib modules may have their own configuration sections. These sec‐
        tions all begin with a module statement. More  details  about  specific
        mib modules may be found in the module sections below.
               module <module-name>
        Module sections may be surrounded by conditional statements. This avoid
        parse errors if those modules are not installed.
               ifdef <module-name>


        The system module require its own section which must contain  the  fol‐
        lowing statements
        Contact  person for this managed node, together with information on how
        to  contact  this  person.  This  will  become  sysContact.0   in   the
               contact <string>
        The  physical  location  of  this  node  (e.g., ‘telephone, closet, 3rd
        floor’).  This will become sysLocation.0 in the SNMPv2-MIB.
               location <string>


        The ups module require its own section which must contain the following
        Specify  the  hostname  of APC UPS Power Management daemon. The default
        port is 6543.
        Since the module uses non-blocking i/o to communicate to the  ups  dae‐
        mon,  you  are  strongly encouraged to only specify servers on the same
        host (preferably localhost).
               apcupsd ( <hostname> | <address> ) [ : ( <service> | <port> ) ]
        A string identifying the UPS. This will become  upsIdentName.0  in  the
               identifier <string>
        A  string  identifying  the  devices attached to the output of the UPS.
        This will become upsIdentAttachedDevices.0 in the UPS-MIB.
               attached <string>
        tinysnmpd(8), apcupsd(8)


        Written by Abraham vd Merwe <>