openvpn initscript no longer details the VPNs started
Bug #264966 reported by
Thierry Carrez
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openvpn (Ubuntu) |
Fix Released
|
Low
|
Thierry Carrez |
Bug Description
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)
----------------
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.
Related branches
To post a comment you must log in.
Proposed debdiff (also includes fix for bug #251641). begin_msg + a log_daemon_msg for each VPN considered.
Changed use of log_progress_msg to log_action_
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.