Fix trusted path

When configuring the plugins you have the option to specify a trusted path with --with-trusted-path. This option seems to have been deprecated at some point for unknown reasons and had typically had no affect. This commit makes this option work again for those who have a desire to use it. There should be no affect on those who have not chosen to specify a trusted path.
Remove unnecessary whitespace in Makefile.am
Merge pull request #1234 from skottler/plugin_makefile_whitespace

Remove unnecessary whitespace in Makefile.am
Add travis config
travis-ci: Enable IRC notification
travis-ci: Add clang and gcc as compiler
travis-ci: Move all into install target

just keeped 'make' in script target
travis-ci: Update package list in before_install
[skip ci]
travis-ci: Make use of before_script target
travis-ci: Add configuration for Coverity Scan

Run Coverity Scan builds on Travis CI, but only when pushing into the
"coverity" branch.
travis-ci: Enable email notifications

Have Travis CI send build failure and recovery notifications to the
team@ list.
travis-ci: Cosmetic changes

Use two spaces for indentation.
travis-ci: remove heading dash accordingly docs
check_ssh: Reverting a387120

This seems to result into more problems in the wild then before 'fixing' it

Closes Debian #739254
Reopen Debian #734811
check_procs test fails if there is no user with uid 501

thats because check_procs verifys there is a user for a
given uid filter. So even we use sample data for this
test, we still need a real user.

Signed-off-by: Sven Nierlein <Sven.Nierlein@consol.de>
travis-ci: Adjust "branch_pattern"

Modify the "branch_pattern" for the Coverity add-on so that it also
matches "coverity/master" and "coverity/maint".
travis-ci: Don't use Clang

Currently, there doesn't seem to be a way to configure Travis CI to omit
the Clang build on the coverity/* branches.

See: https://github.com/travis-ci/travis-ci/issues/1975
check_swap: Fix the plugin name that appears in the comment

Signed-off-by: Davide Madrisan <davide.madrisan@gmail.com>
Rename configure.in to configure.ac

The old name has been deprecated years ago.  The Autoconf documentation
says:

| Previous versions of Autoconf promoted the name configure.in, which is
| somewhat ambiguous (the tool needed to process this file is not
| described by its extension), and introduces a slight confusion with
| config.h.in and so on (for which `.in' means "to be processed by
| configure").  Using configure.ac is now preferred.

[ https://www.gnu.org/software/autoconf/manual/autoconf.html ]
configure.ac: Support --disable-maintainer-mode

This

| allows you to choose whether the so called "rebuild rules" should be
| enabled or disabled.  With AM_MAINTAINER_MODE([enable]), they are
| enabled by default, otherwise they are disabled by default.  In the
| latter case, if you have AM_MAINTAINER_MODE in configure.ac, and run
| `./configure && make', then make will *never* attempt to rebuild
| configure, Makefile.ins, Lex or Yacc outputs, etc.  I.e., this
| disables build rules for files that are usually distributed and that
| users should normally not have to update.
|
| The user can override the default setting by passing either
| `--enable-maintainer-mode' or `--disable-maintainer-mode' to
| configure.
|
| People use AM_MAINTAINER_MODE either because they do not want their
| users (or themselves) annoyed by timestamps lossage (see CVS), or
| because they simply can't stand the rebuild rules and prefer running
| maintainer tools explicitly.

[ https://www.gnu.org/software/automake/manual/automake.html ]