I am one of thoes guys who is constantly tinkering with my configurations. Well, I went and changed my network from using etc/hosts to using bind 8. In so doing I added a subdomain to my FQDN. This was so I could distinguish between internal and external systems. When I did this several things stopped working. I had to hunt down several places where the FQDN needed to be changed. Happily several of these were controled by rc.config. Nothin' like one-stop shoppin'! There were still a few other places where changes were required. It would be nice, and perhaps I just haven't tried hard enough, to have an environment variable that could be referenced in config files so that when this variable is changed all configurations simply fall in line. Yeah, I'm asking for a lot, and such "conviences" oftwn come with hidden costs. The part that gave me the dickens was the DOC_HOST, and the help system. I don't remember all the changes I had to make, but it took a little while. Another little trick I pulled on myself was changing from inetd to xinetd. This caused my http-rman to stop working. Since all the other problems with the help system were domain name related, I assumed this one was as well. I finally took a look at xinetd.conf and compared it to inetd.conf. I realized that http-rman was not being started by xinetd. Is this something that SuSEconfig should be expected to handle? That is, should SuSEconfig maintain the configuraton of xinetd.conf -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/