acking branch 'origin/jcb-proposed_master' into proposed_master

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.

If wrsLeapSecStatusDetails returns 'leapSecFileExpired' then it will be
propagated to wrsLeapSecStatus as follow:
- Timing mode is GM or FR : Warning
- Timing mode is BC: Ok

The conversion has been fixed now for negative values.

Conflicts:
	userspace/ppsi

Compiled from wrpc-sw commit:
3e4f8d1 rt_cpu: disable PLL verbose mode by default (output on UART is blocking and greatly slows down LDPC port calibration in the WR Switch)

Alessandro Rubini authored 5 years ago and Grzegorz Daniluk committed 5 years ago

If you call lldpcli from a program, stdout will be fully buffered, and
we won't get back the result of "show neighbors" (nor anything else).
Expectedly, stderr messages are delivered immediately.

You can verify this by running "cat | lldpcli", give comamnds and
then exit with ctrl-D (EOF).

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

- Remove all references to HA (+ L1SYNC) in KConfig files
- Update some help description

SNMP checkes whether monitored daemons where restarted by looking
at the respective /tmp/start_cnt_X file. Such file is not created
if a daemon is disabled in configuration (dotconfig). Such
disabling is a new feature. It turns out that not all of SNMP
deamon was updated to accommodate it. The SNMP daemon was checking
at start which daemons are disbled but later did not use this
info in wrsStartCntGroup and the startCnt of the disabled deamons
was attempted to be checked, resulting in an error. This has
been fixed.

As monit process is started after other processes, it does not take into
account  the 'unmonitor' messages sent from start scripts (ldap.sh,
...). This generates error messages at startup.

To avoid that, the configuration of monit is set now dynamically in the
apply_dotconfig script. All disabled processes are then removed from the
configuration to avoid errors due to process start order.
Also the first monitoring cycle is postponed by 30s at startup.