Re: Setting gconf/dconf keys in kickstart

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/03/2011 11:52 PM, Hugh Brown wrote:
[snip]
----8<---
su - gdm -s /bin/bash --command='
for line in `dbus-launch`; do export "$line"; done;
/usr/libexec/dconf-service &
GSETTINGS_BACKEND=dconf gsettings set org.gnome.desktop.sound
event-sounds false;
exit' 2> /dev/null
----8<---


eval `dbus-launch` should do everything in your for loop.

Thanks. It's not really my for loop. All credit goes to the Arch Linux wiki where I found this script.

You might be able to revert to just setting
/desktop/gnome/sound/event_sounds in the mandatory tree w/ the hope that
the gdm user inherits those settings.

I think I tried that late last night and iirc GDM did not inherit.

As to things, not exiting, the anaconda webpage describes this scenario:

http://fedoraproject.org/wiki/Anaconda/Kickstart#Chapter_5._Post-installation_Script

If your script spawns a daemon process, you must make sure to close
stdout and stderr. Doing so is standard procedure for creating daemons.
If you do not close these file descriptors, the installation will appear
hung as anaconda waits for an EOF from the script.

Killing dconf-service takes care of closing those file descriptors.

Thank you for the link (and help). I understand now why it was hanging.

Regards,
Patrick

_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list


[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux