openvpn initscript no longer details the VPNs started

[Thierry Carrez]

Binary package hint: openvpn

OpenVPN init script handles the start of zero-to-many VPNs, based on your configuration.

When starting, the openvpn initscript shipped on 8.04 detailed the names of the VPNs you started:
----------------
 * Starting virtual private network daemon.
 * server (OK)
                                                                         [ OK ]
----------------

With the one shipped in intrepid, you no longer have the information:
----------------
 * Starting virtual private network daemon [ OK ]
----------------

This is linked to a change in Debian where they now use log_progress_msg, which is a noop on Ubuntu.

[Thierry Carrez (ttx)]

Proposed debdiff (also includes fix for bug #251641).
Changed use of log_progress_msg to log_action_begin_msg + a log_daemon_msg for each VPN considered.
The result is :

-------------------------------
 * Starting virtual private network daemon(s)...
 * Autostarting VPN 'client2' [ OK ]
 * Autostarting VPN 'client' [ OK ]
-------------------------------

I also fixed the stop/restart/cond-restart/reload... messages.

[Thierry Carrez (ttx)]

Note that it creates a delta with Debian that might not be worth it.

[Thierry Carrez (ttx)]

Final debdiff with a few cosmetic changes

[Launchpad Janitor (janitor)]

This bug was fixed in the package openvpn - 2.1~rc9-3ubuntu2

---------------
openvpn (2.1~rc9-3ubuntu2) intrepid; urgency=low

  * debian/openvpn.init.d:
    - Added 'status' action to init script (LP: #251641)
    - Restored per-VPN result messages by using log_action_begin_msg and
      one log_daemon_msg per VPN instead of log_progress_msg (LP: #264966)
  * debian/control: Added lsb-base>=3.2-14 depend to allow status_of_proc()

 -- Thierry Carrez <email address hidden> Tue, 09 Sep 2008 10:45:45 +0200