Bug 89092 - Gpilotd should be configured for startup in redhat-config-services
Gpilotd should be configured for startup in redhat-config-services
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-services (Show other bugs)
9
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-04-17 11:27 EDT by Linus Walleij
Modified: 2007-04-18 12:53 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-04-18 13:38:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Linus Walleij 2003-04-17 11:27:07 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
The service manager is brilliant, but unfortunately the control of the gpilotd
daemon has been forgotten. Actually, it has never been possible to configure
this daemon to start up automatically, so please add it to redhat-config-services.

Version-Release number of selected component (if applicable):
redhat-config-services-0.8.4-1

How reproducible:
Always

Steps to Reproduce:
1. Start you machine
2. ps aux <pipe> grep gpilotd
3. Daemon isn't started
    

Actual Results:  The daemon was not started.

Expected Results:  Expected to be able to control this daemon from
redhat-config-services

Additional info:
Comment 1 Daniel Walsh 2003-04-18 13:38:40 EDT
redhat-config-services is a tool for managing system wide services/daemons.  It
basically manages the startup scripts in the /etc/init.d dirctory.  If the
daemon does not use a init.d startup script redhat-config-services does not deal
with it. 

Note You need to log in before you can comment on or make changes to this bug.