Bug 89877 - No way to autostart gpilotd
Summary: No way to autostart gpilotd
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-pilot
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-04-29 08:28 UTC by Linus Walleij
Modified: 2007-04-18 16:53 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-04-29 14:54:56 UTC
Embargoed:

Attachments (Terms of Use)

Description Linus Walleij 2003-04-29 08:28:07 UTC 
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):
gnome-pilot-0.1.71-2

How reproducible:
Always

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 14:54:56 UTC 
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 15:32:47 UTC 
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.