Since oafd runs on behalf of the user, not the system, it makes more sense
for it to run in ~ than /.

Long story:

There was a bug in gnome-gtkhtml-editor that crashed it maybe every 10th
time it ran. The stack trace from bug-buddy wasn't useful because of how
the signal handler tends to munge the important stack frame. I didn't want
to have to run gnome-gtkhtml-editor by hand every time, because the bug
usually didn't happen, and it would get annoying quickly to have to do
that. So what I wanted to do was set GNOME_DISABLE_CRASH_DIALOG in oafd's
environment and then let gnome-gtkhtml-editor crash and leave a nice
useful core file when it hit the bug. Alas, oafd runs in /, and therefore
so do all of the components it launches, making it hard to get core files
from them. But I built a hacked oafd, and it was good.



------- Additional Comments From mjs@noisehavoc.org 2001-08-26 23:27:40 ----

The reason it doesn't run in the user's homedir is a specific bug report
about a user's NFS home directory not getting properly unmounted because
oafd was hanging around using it as it's cwd. Maybe this can be reconsidered
when / if oaf automatically exits when idle.




------- Additional Comments From mjs@noisehavoc.org 2001-08-26 23:27:49 ----

The reason it doesn't run in the user's homedir is a specific bug report
about a user's NFS home directory not getting properly unmounted because
oafd was hanging around using it as it's cwd. Maybe this can be reconsidered
when / if oaf automatically exits when idle.




------- Additional Comments From danw@ximian.com 2001-09-04 10:34:43 ----

Is there a bug for "oaf should exit when idle" that this should depend on then?

Another workaround would be for oaf to chdir itself to /, but then chdir its
child processes to ~. (And if those processes don't exit, it's their fault,
not oaf's.)



------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 21:18 -------