Extra forks on automount initialisation & HUP signal

Imported from Debian bug http://bugs.debian.org/678555:

Package: autofs
Version: 5.0.6-2
Severity: important
User: <email address hidden>
Usertags: origin-ubuntu quantal ubuntu-patch

After merging 5.0.6-2 for Ubuntu I have noticed that upstart init daemon
was tracking the wrong PID of the daemon. [1]

This resulted me into digging what has changed and I noticed the three
patches, which I have attached to this email.

These patches [0001-0003] do three things:

* Check mount.nfs version to be >= 1.1.1
* Check kernel version is >= 2.6.22
* Do above by calling nfs_version_check at pre-demonisation, hence
upstart ending up tracking `mount.nfs -V` call
* all for the sake of figuring out if probing optimisation can be used
(or something, not too sure):

"""
The change to have the kernel process text based mount options can
introduce lengthy timeout waits when attempting a mount to a host
that is not available.

To avoid these waits autofs should probe singleton mounts if it
thinks mount.nfs will pass text options to the kernel (which of
course implies the kernel supports this).
"""

But, mount.nfs 1.1.1 is acient and so is linux kernel 2.6.22... so I'm
thinking to make this a no-op. and simply remove those checks. See mine
Remove-*.patch attached.

With that patch I want to revert the upstream patches [0001-0003].

Setting priority to important as this is change of daemon behaviour and
resource waste to fork calls like this. Feel free to lower severity, if
you wish.

[1] Upstart does not rely on pidfiles, instead it counts forks/clones
and chooses the correct pid to track, such that it notices if it dies /
gets killed. This is more reliable than pidfiles. Upstart can also run
daemons in foreground mode.

--
Regards,
Dmitrijs.