I recently modified my syslog.conf file and then went to yast to disable/enable the syslogd service as as quick and dirty way to get syslog.conf reread. Big mistake. When you disable syslog in YAST a large number of other services are automatically disabled for you. That's not so bad, but when you reenable syslog those services are not turned back on. I have gone back and reenabled those services as best as I could but I would appreciate it if someone could point me to a list of services that are turned on in a default installation of Suse 9.2 to make sure that I'm not overlooking something. On a related matter, it __seems__ that disable/enable syslogd caused powersaved to be enabled. I'm only 10% confident of this (don't want to mess with syslogd to test this out) but powersaved was enabled after my first disable/enable sequence. Now it might have been enabled earlier but I don't know how. In fact it was the powersaved daemon that made me realize I had a problem because I saw that a stream of error messages were being syslogged by the system saying that it could not connect to the powersaved daemon which led me to fire up the runlevel editor in YAST and that's when I saw a lot of important services were turned off. Thanks, Patrick