This is the crux of the problem...since the change from rc.config to the "new boot concept" where did the startup switches go to? [Remember in rc.config] START_HTTPD="yes" START_NAMED="yes" (START_BIND..DONT REMEMBER OFF-HAND) If using SuSEConfig = yes then when a new service daemon like httpd or bind is installed then the Yast tool should also set the service to be automatically started (even after a reboot). Unfortunately, they do not have any docs that state...you used to do this in v6.3 but now you must do this or it wont work. -----Original Message----- From: Keith Winston [mailto:kwinston@twmi.rr.com] Sent: Tuesday, April 30, 2002 11:28 AM To: suse-linux-e@suse.com Subject: Re: [SLE] Yast2 BUG On Tue, Apr 30, 2002 at 10:37:20AM -0500, kevin.wilson@comtrol.com wrote:
When installing Bind and Apache using Yast2 the appropriate service entries were not put in the inittab file that will allow the services to be automatically started after the machine is rebooted.
No services are started in inittab, that's where gettys are spawned and the runlevel is determined. To control which services start at which runlevels, go back to YaST2 / System / Runlevel Editor and click on the Runlevel Properties button. Most people boot into either runlevel 3 or 5. Best Regards, Keith -- LPIC-2, MCSE, N+ Got spam? Get spastic http://spastic.sourceforge.net -- 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 archives at http://lists.suse.com
On Tue, Apr 30, 2002 at 11:44:09AM -0500, kevin.wilson@comtrol.com wrote:
This is the crux of the problem...since the change from rc.config to the "new boot concept" where did the startup switches go to?
[Remember in rc.config]
START_HTTPD="yes" START_NAMED="yes" (START_BIND..DONT REMEMBER OFF-HAND)
Ah, yes, I remember, although the runlevel editor was introduced in either 7.2 or 7.3. I know it was in 7.3. Really, the new way is much more standard than having START variables in /etc/rc.config. The runlevel editor is covered in the manuals in the boxed set, but I don't remember if it was listed in the update from 7.3 to 8.0 section. The new /etc/sysconfig mechanism is different, but I do think it is an improvement, again, with the exception of PCMCIA/hotplug/wireless, but I've complained enough about that one :) Best Regards, Keith -- LPIC-2, MCSE, N+ Got spam? Get spastic http://spastic.sourceforge.net
* Keith Winston; <kwinston@twmi.rr.com> on 30 Apr, 2002 wrote:
On Tue, Apr 30, 2002 at 11:44:09AM -0500, kevin.wilson@comtrol.com wrote:
This is the crux of the problem...since the change from rc.config to the "new boot concept" where did the startup switches go to?
[Remember in rc.config]
START_HTTPD="yes" START_NAMED="yes" (START_BIND..DONT REMEMBER OFF-HAND)
Ah, yes, I remember, although the runlevel editor was introduced in either 7.2 or 7.3. I know it was in 7.3. Really, the new way is much more standard than having START variables in /etc/rc.config. The runlevel editor is covered in the manuals in the boxed set, but I don't remember if it was listed in the update from 7.3 to 8.0 section.
according to support database http://sdb.suse.de/sdb/en/html/rc-sysconfig-8-0.html find /etc/sysconfig -type f | xargs grep KBD_NUMLOCK will find the file which has the KBD_NUMLOCK feature :-) also http://sdb.suse.de/sdb/en/html/mmj_network80.html (as it was posted earlier by Mads) describes the new settings Now back to my reading to discover new and not liked YaST2 features (so far it looks I am administering Win 2K click next please and honest I have bever used yast2 and actuallynever installed this time looks I have to :-( -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
participants (3)
-
Keith Winston -
kevin.wilson＠comtrol.com -
Togan Muftuoglu