Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 500570

Summary:	RFE: ipsec-tools: racoon daemon should have an init script
Product:	Red Hat Enterprise Linux 5	Reporter:	Tomas Hoger <thoger>
Component:	ipsec-tools	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE <qe-baseos-auto>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.3	CC:	wmealing
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-05 16:27:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tomas Hoger 2009-05-13 10:37:53 UTC

Description of problem:
ipsec-tools package should provide init script to start / stop racoon daemon.  Current Fedora ipsec-tools packages already provide the init script for racoon.

This was previously notabugged in bug #136901 stating that initscripts's if{up,down}-ipsec are expected to start racoon daemon as needed.  However, racoon may need to be restarted (not only reloaded) in some cases, for example during the installation of the updated packages.  if{up,down}-ipsec only starts and reloads racoon, never stops it.  Manual restart may cause racoon to run with incorrect context (bug #500395).

Version-Release number of selected component (if applicable):
# rpm -q ipsec-tools
ipsec-tools-0.6.5-13.el5

Additional info:
In the long term, if{up,down}-ipsec should probably get changed to call init scripts instead of running racoon directly.

Comment 1 Tomas Mraz 2012-03-05 16:27:12 UTC

We do not plan to resolve this issue in Red Hat Enterprise Linux 5 update release.