Bug 89877 - No way to autostart gpilotd
No way to autostart gpilotd
Product: Red Hat Linux
Classification: Retired
Component: gnome-pilot (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Depends On:
  Show dependency treegraph
Reported: 2003-04-29 04:28 EDT by Linus Walleij
Modified: 2007-04-18 12:53 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-04-29 10:54:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
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-29 04:28:07 EDT
Description of problem:
There is no way top configure RedHat to start gpilotd automatically on boot. The
only way to start gpilotd is to start the "settings" program. A script should
possibly be added to the init.d scripts to autostart gpilotd in runlevel 5 if
the user choose to install this package.

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

How reproducible:

Steps to Reproduce:
1.Start RedHat
2.ps aux
3."gpilotd" is not running.

Actual Results:  No daemon was running.

Expected Results:  The gpilotd daemon should be started on startup.
Comment 1 Jeremy Katz 2003-04-29 10:54:56 EDT
gpilotd has to be run by the user and not on a system level.   Saving your
session after configuring your pilot makes it so that gpilotd will get restarted
on subsequent logins.
Comment 2 Miloslav Trmac 2003-04-29 11:32:47 EDT
OK, how about making this a documentation bug about gnome-pilot?
Its strings don't mention the word 'session' at all,
and the RHL documentation doesnt either AFAIK.

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