Bug 673705

Summary: init script status command dysfunctional
Product: [Fedora] Fedora Reporter: JW <ohtmvyyn>
Component: openvpnAssignee: Steven Pritchard <steve>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: huzaifas, steve
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 15:52:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
patch to show proper service status none

Description JW 2011-01-30 01:11:05 UTC 
Description of problem:
The installed /etc/rc.d/init.d/openvpn init script "status" command is dysfunctional for a number of reasons.

Firstly, it lies about where it is writing its information: /var/log/messages is only used if the openvpn instance does not have a log or log-append setting, and also only if your syslog.conf directs certain messages to /var/log/messages.  

Secondly the output which is written to the log file as a result of the "status" command is not status but instead only statistics.  No information about the state of the openvpn link is written to the log file. The statistics information also consists of multiple log lines which might be interspersed with other log output.  Perhaps the command should really be a supplementary "statistics" command.

Thirdly, it really isn't standard practice for a "status" command to write output to an arbitrary/indeterminate log file.  The status output should be something that is directly visable and usable: perhaps just simple information as to whether the openvpn instances are alive and running, and their pid's perhaps.

Version-Release number of selected component (if applicable):
openvpn-2.1.1-2

How reproducible:
Always

Steps to Reproduce:
1. service openvpn status
  
Actual results:
1. "Status written to /var/log/messages"

Expected results:
1.
abc.conf 19111 running
def.conf 19120 running
ghi.conf - stopped


Additional info:
Has been dysfunctional for a long time.
Comment 1 JW 2011-01-30 01:30:03 UTC 
Created attachment 475976 [details]
patch to show proper service status

This patch modifies samples-scripts/openvpn.init (installed as /etc/rc.d/init.d/openvpn) to show proper instance status, with the original status command renamed to "statistics".
Comment 2 Fedora End Of Life 2012-08-16 15:52:49 UTC 
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping