[551] in athena10
Disposition of local GConf2 modifications
daemon@ATHENA.MIT.EDU (Robert A Basch)
Wed Oct 1 18:14:18 2008
Message-Id: <200810012213.m91MDWJf020786@abulia.mit.edu>
To: athena10@MIT.EDU
Date: Wed, 01 Oct 2008 18:13:32 -0400
From: Robert A Basch <rbasch@MIT.EDU>
For Athena 9, we have local modifications to GConf2 for the following
purposes:
1) Run a separate gconfd in each session.
2) Lock the backend when syncing.
3) Invoke gconfd under dustbuster to ensure it is killed at logout.
4) Point at a temporary storage source instead of the home directory
for a NOCALLS session.
5) Set the ACL of the .gconf and .gconfd directories in $HOME to make
them private.
As things stand now, I believe we will not need to do source
modifications for any of these:
As discussed in previous email, we have decided to desupport 1) and 2).
We plan to rely on the GNOME session manager to handle 3) (though I
have noticed that the gconfd process does not always die at the end of
a session, so we may need to address that).
For 4), we plan to replace the NOCALLS functionality with the gdm
failsafe session. I think we actually do not want to use a temporary
storage source in a failsafe session, as the user may need to fix
settings stored in GConf2 in such a session, so no work is needed
here.
That leaves 5). I plan to address this by adding a wrapper for
gconfd-2, which will create GConf2's subdirectories in an AFS home
directory if needed, and set their ACLs appropriately. A slight
complication is presented by the configuration of the .gconf
directory done by debathena-gconf2-config, which configures GConf2
to use .gconf.debathena-DIST instead of .gconf for an AFS home
directory. I will deal with this by having the wrapper parse the
/usr/share/debathena-gconf2-config/gconf.afs file to determine the
correct .gconf directory to use.
Bob
