Bug 51043 - GNOME leaves processes hanging around after exit
Summary: GNOME leaves processes hanging around after exit
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-core   
(Show other bugs)
Version: 7.3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2001-08-06 20:54 UTC by Chris Evans
Modified: 2007-04-18 16:35 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-06 21:32:08 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Chris Evans 2001-08-06 20:54:41 UTC
Description of Problem:

Exiting GNOME leaves two processes hanging around.

How Reproducible:


Steps to Reproduce:
1. At the GDM login screen, log into GNOME
2. Log out
3. Log in at the console
4. Do "ps -x"

Actual Results:

"gconfd" and "oafd" are still running.

Expected Results:

"gconfd" and "oafd" were shut down with the rest of the GNOME
processes upon GNOME exit.

Additional Information:

Comment 1 David Mason 2001-08-06 20:59:25 UTC
There really is no reason for these processes to stop. GConf is a per
application configuration registry that can be used by apps that are graphical
or not. oafd allows CORBA enabled apps to find CORBA objects - again not a
graphical or non-graphical item.

Comment 2 Chris Evans 2001-08-06 21:28:01 UTC
There is definite reason for these processes to stop. When
a user is totally logged out, they should not consume
Imagine a publicly accessible terminal in a lab - I'm sure
you have lots of installations like this. Do you really want
to waste two processes per user who has ever logged in to the
GNOME desktop?!

Comment 3 Havoc Pennington 2001-08-06 22:12:53 UTC
Current rawhide gnome-core (well, I'm not sure it synced yet, but whatever I
built on Friday or so) has a terrible hack to kill off oafd on logout, assuming
you log out cleanly. If you ctrl-alt-backspace, you're on your own.

gconfd will exit after 15 minutes if it is unused. If it doesn't exit then
something is probably using it. I could change this time to 5 minutes, I'm not
sure what would be best.

If this contrasts with observed behavior, please reopen.

Comment 4 Glen Foster 2001-08-06 22:29:39 UTC
This defect is considered SHOULD-FIX for Fairfax.

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