Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 84426 - oafd is left running after logging off
oafd is left running after logging off
Product: Red Hat Linux
Classification: Retired
Component: oaf (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Havoc Pennington
Depends On:
  Show dependency treegraph
Reported: 2003-02-16 14:37 EST by Stephen Walton
Modified: 2007-04-18 12:51 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-10-09 00:12:24 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 Stephen Walton 2003-02-16 14:37:47 EST
Description of problem:

After logging on and off via Gnome, oafd is left running.  This is a problem in
an environment where multiple login clients share the same home directory from a
server, because it results in an error message about one's preference files
still being in use when one logs into another machine.

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


How reproducible:


Steps to Reproduce:
1. Log into a machine which is in an NFS/NIS or NFS/LDAP environment in which
login directories are stored on a central machine.
2. Log off of that machine and into another one on the same machine.
Actual results:

A popup box appears on the second login, "Your preference files are in use on
another machine."

Expected results:

No such message.

Additional info:

I am attributing this problem to oafd since it is the one process left running
after a login/logoff sequence.
Comment 1 Havoc Pennington 2003-02-16 14:43:16 EST
oafd is GNOME 1.4 stuff, GNOME 2 in 8.0 should not start it. Evolution may start
it if you run Evolution.

the preferences message is in fact about gconfd, but gconfd should be existing
after 2 minutes without use (which is probably why you don't notice that process
by the time you're looking for it).
http://www.gnome.org/projects/gconf/ also describes a workaround setting 
GCONF_LOCAL_LOCKS env variable.
Comment 2 Stephen Walton 2003-02-16 19:52:29 EST
Thanks for both pieces of info.  You're correct that I'm running Evolution.  I
suppose this should be marked resolved somehow, but I'm not sure;  it isn't
exactly NOTABUG but seems to be scheduled to be fixed in Gnome 2.2 judging from
the text at the above link.
Comment 3 Havoc Pennington 2003-02-16 20:08:48 EST
well, I'm not sure it's notabug, but probably the evolution guys are planning 
to fix it by moving to gnome 2, so it all comes out the same. you might 
search bugzilla.ximian.com, may be more info there.
Comment 4 Gerald Teschl 2003-03-06 02:51:32 EST
I just see the same thing on all of our boxes after a fresh install of 8.0.
On every box there are about 10 oafd processes running from different users.
This is a huge mess.
Comment 5 Gerald Teschl 2003-03-06 03:09:43 EST
Wow! I just found a box with 30 oafd processes running, using 25% of the memory.

BTW, even on a current beta system, evolution does not seem to be the only
program using oaf:

$ rpm -q --whatrequires oaf
Comment 6 Havoc Pennington 2003-03-06 09:52:13 EST
those other packages are all libraries, evolution is the only app that uses it.
Comment 7 David Deaderick 2003-04-02 09:30:08 EST
I am seeing a similar occurence on Advanced Server 2.1 runing Oracle 9iAS.  The 
oafd process is remaining long after I log off of the oracle user ID, even with 
all Oracle processes shutdown.  The Gnome RPM is in Red Had Enterprise 
Linux Advanced Server 2.1

UID        PID  PPID  C STIME TTY           TIME CMD
oracle    6267     1  0 09:20 ?         00:00:00 oafd --ac-activate --ior-

Any ideas how to get this to go away?
Comment 8 Havoc Pennington 2003-10-09 00:12:24 EDT
Rendered irrelevant with the move to Evolution 1.4, there should not be any apps
starting up oafd anymore.

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