Turning off gconfd

dive · 03-21-2006, 11:59 AM

I see from /var/log/messages that the gconfd daemon is running throughout the day. I'm not using Gnome although I do run some gtk apps like Gaim and Gimp.

Is there any way of permanently turning gconfd off (short of chmod'ing -x it)? Or do I need it for gtk or other (gnomish) apps?

I tried shutting it down with gconftool-2 --shutdown and then restarting Gaim but the daemon doesn't start up so I assume it isn't needed.

I can't seem to find out where it is starting up from.

rahulk · 03-22-2006, 05:37 AM

to stop the daemon from running after reboot use

chkconfig gconfd off

you need to log in as root. also you can check the runlevels for which youer daemon is currently active.

chkconfig --list | grep gconfd

it will give all the runlevels as well as on/off.

reddazz · 03-22-2006, 05:42 AM

Quote:

Originally Posted by rahulk

to stop the daemon from running after reboot use

chkconfig gconfd off

you need to log in as root. also you can check the runlevels for which youer daemon is currently active.

chkconfig --list | grep gconfd

it will give all the runlevels as well as on/off.

I don't think slackware using chkconfig. It uses bsd style scripts so you would need to do something like "chmod -x gconfd" in /etc/rc.d.

dive · 03-22-2006, 08:43 AM

I tried chmod -x it earlier and noticed that Firefox complained that it couldnt start it. I can only imagine that FF is using it as a way to tell what programs should run when launching files from the download window or something similar.

reddazz · 03-22-2006, 09:45 AM

Quote:

Originally Posted by dive

I tried chmod -x it earlier and noticed that Firefox complained that it couldnt start it. I can only imagine that FF is using it as a way to tell what programs should run when launching files from the download window or something similar.

Well if Firefox uses gconfd then you'll have to leave it as it is.

dive · 03-22-2006, 09:53 AM

What I've done now is edited /etc/syslog.conf:

Added user.none; to -/var/log/messages

Added a new line:

user.* -/var/log/user

Now at least the gconfd start/stopping messages get logged elsewhere, leaving /var/log/messages cleaner.