Bug 221543

Summary:	[DOCUMENTATION] Please provide an exact procedure to install & use the startup scripts in Fedora Core 6
Product:	[Retired] 389	Reporter:	Răzvan Sandu <rsandu2004>
Component:	Install/Uninstall	Assignee:	Nathan Kinder <nkinder>
Status:	CLOSED DUPLICATE	QA Contact:	Orla Hegarty <ohegarty>
Severity:	high	Docs Contact:
Priority:	medium
Version:	1.0.4
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://directory.fedora.redhat.com/wiki/Howto:SysVInit
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-01-09 22:35:19 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 Răzvan Sandu 2007-01-05 00:10:52 UTC

Description of problem:

Hello,

The scripts provided at http://directory.fedora.redhat.com/wiki/Howto:SysVInit
seems to be, for the moment, the only way to automate Fedora DS' startup (since
the base DS .rpm doesn't include such scripts).

Please provide an exact, step-by-step procedure to install and use these three
scripts on a stock FC6 installation (standard place for the scripts in the
filesystem, Unix permissions, SELinux context, the recommended way to integrate
with the other startup scripts in initscripts, etc.)


Many thanks,
Razvan


Version-Release number of selected component (if applicable):
fedora-ds-1.0.4-1.FC6.i386


How reproducible:
Always.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
There is no step-by-step procedure to (manually)integrate the three provided
scripts with the rest of the initscripts package.

Expected results:
The above procedure must exist, since it's a critical barrier in deploying and
using Fedora Directory Server in real-life implementations.


Additional info:

Comment 1 Rich Megginson 2007-01-09 22:35:19 UTC


*** This bug has been marked as a duplicate of 164032 ***

Comment 2 Răzvan Sandu 2007-01-10 15:59:46 UTC

Is bug 164032 a private bug ? I cannot acces it ...

Thanks,
Răzvan

Comment 3 Chandrasekar Kannan 2008-08-11 23:49:59 UTC

Bug already CLOSED. setting screened+ flag