[sabayon] Add a shutdown for gconf before applying the profile to ensure there's no existing gconfd hanging ab
- From: Scott Balneaves <sbalneav src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [sabayon] Add a shutdown for gconf before applying the profile to ensure there's no existing gconfd hanging ab
- Date: Fri, 19 Feb 2010 16:03:24 +0000 (UTC)
commit 10a8b01ff9b5457038a790731307887110ed5e67
Author: Scott Balneaves <sbalneav ltsp org>
Date: Fri Feb 19 10:08:04 2010 -0600
Add a shutdown for gconf before applying the profile to ensure there's no existing gconfd hanging about
admin-tool/sabayon-apply | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
---
diff --git a/admin-tool/sabayon-apply b/admin-tool/sabayon-apply
index 5d69782..c94f001 100755
--- a/admin-tool/sabayon-apply
+++ b/admin-tool/sabayon-apply
@@ -36,6 +36,7 @@ if __name__ == '__main__':
import sys
import optparse
import shutil
+ import subprocess
from sabayon import userprofile
from sabayon import config
@@ -98,6 +99,16 @@ if __name__ == '__main__':
pass
#
+ # Shutdown any existing gconfd server. Since we're going to be
+ # applying a new profile, with new gconf keys, we should shutdown any
+ # existing gconfd process, so that the new keys will be applied when
+ # gnome-session starts back up. Theoretically there shouldn't be one,
+ # but sometimes they "hang around".
+ #
+
+ subprocess.call (["gconftool-2", "--shutdown"])
+
+ #
# Begin the process of determining WHICH profile to apply.
# We have 4 possibilities, rated in order of priority (highest first)
# 1) We've been passed a profile on the command line. We'll apply
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]