The problem was as follows:
- there were two nodes with the same MAC address, sending traffic
  at high frequency
- the above triggers a lot of learning requests to rtud, as a result
- rtu HASH table representation in SHMEM is constantly udpated
- the aging process runs in background (separate process) and updates
  the time the entry was last used.

The update process could not the time of last access in the HASH
table in SHMEM because the learing process was constantly occupying
the SHMEM. The age out process was never aging out entry (even if this
one is within mutex) since the access time was never updated.

Thus, now both, update of last access time and age-out process are
both within mutex that allows the learning and aging-out processes
to both access SHMEM and HW.

When using wrsw_vlans to update config, by default, display which
config has been updated and which has not been updated.

Do not display updates when reading from file or explicitely
requested to be silent with "-q" option.

Related to issue #202

There were few bug/problems:
1) Setting of tag/untag worked only when enabling tagging,
   if tagging was later set to disabled, this did not take effect.
2) This affected default configuration of tag/untag function
   when qmode of port was set. Thus, when changing to TRUNK
   from ACCESS, the port would keep untagging

The value of temperature that is read from register of the T100
sensor is encoded with twos complement on 16 bits. The encoding
was not proper thus it worked fine but only for positive values
of temperature. Added function that properly interprets the
value of temp read from sensor's regsister.

Bug fix for PPS generation

Fix display errors for diagnostics

If it is disabled, it's commented out in dot-config, if it is enabled,
it appears with "=y"

The fields in this table were not really filled in after
substantial changes to the PPSi architecture regarding
servo (HA-related). Filling in of the fields in this
table had to be redone. This commit fixes filling in
most of the fields that were field before. There are still
some fields that are not filled in, tbd.

- update wrsSpllStatusGroup to recognize ver=3
- update wrsSpllStatusGroup and wrsSpllVersionGroup to
  properly complain to syslog when not recognizing version

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Move wrsPtpInstanceName to be the first (after indexes) OID.
Thanks to this, by doing snmpwalk/snmpgetnext of OID wrsPtpInstanceName(.<n>.<m>),
the user gets in a single responce:
--n - a port number
--m - an instance nubmer
--value which is an instance name
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

The list of VLANs is implemented as a string, becasue
SNMP does not allow tables within tables.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

After a general cut in the electrical power supply, the switch can restart before than other generic systems (routeurs, serveurs, DHCP & NTP services,...).
It results that the switch might be not well configured if these services cannot be reached and especially the DHCP service.

So, a new behavior has been introduced to wait for the availability of the DHCP service (if configured) to get the source of the dot-config file and to setup the management port.

A dependency have been added to not allow the option "Force to get the
URL to a dot-config via DHCP" in order to get the source of the
dot-config file. This option is now only available if the "DHCP forever"
option is selected in the management port configuration.

This has been done to avoid to wait forever the availability of the DHCP
service to get the dot-config source while this service is not required
or mandatory for the management port setup.

When the configuration indicates that the network is  forced to use the
DHCP service for its setup (CONFIG_ETH0_DHCP=y), the script waits
forever the availability of the DHCP service.

In the other cases, the behavior remains unchanged.

When the dot-config file is read at startup using the DHCP service to
get the server IP address, the script waits forever the availability of
DHCP service in the following case :
- CONFIG_DOTCONF_SOURCE_FORCE_DHCP=y AND CONFIG_ETH0_DHCP=y

CONFIG_ETH0_DHCP: Set to indicate that the network is forced to use DHCP
for its setup.

In the other cases, the behavior stay unchanged.

The parser must take care of the help text because it can contains
KConfig keywords.
So, this fix identifies help sections and does not parse the help text.