YaSt runlevel display is wrong
SUSE 10.1, KDE 3.5.2 updates. Looking for confirmation that I have found an issue with YaST's Runlevel display. Runlevel starts off in Simple Mode and appears to display the Enabled status correctly. When switching to Expert mode I notice that the Enable status does not _always_ match the Simple Mode status. I almost always select Expert mode ASAP when using YaST Runlevel and began to notice that services I knew to be running showed as "No" in Expert mode. Doing the Refresh on individual processes shows the correct Enabled status. Anyone know of any other command line options to start YaST runlevel in Expert Mode or how to cause a full refresh of all processes' status when in Expert Mode? Thanks, Stan
On Friday 26 May 2006 09:57, S Glasoe wrote:
SUSE 10.1, KDE 3.5.2 updates.
Looking for confirmation that I have found an issue with YaST's Runlevel display.
Hi Stan, After installing 10.1, I immediately upgraded to 3.5.2 level 'a' (for compatibility with my 9.3 and 10.0 Kontact.) I /did/ notice a similar anomaly: I had to manually refresh the status of SuSEFirewall2 after stopping it and restarting it as part of setting up the ntp client. I received the desired 'Success [status 0]' message but I 'double-checked' before closing the module and it did /not/ show 'running' until I refreshed it. I haven't dug into it any further because, well, I don't spend much time in that module ;-) and I was busy... promply forgotten, too, so thanks for the reminder! regards, Carl
On Fri, 2006-05-26 at 10:31 -0400, Carl Hartung wrote:
On Friday 26 May 2006 09:57, S Glasoe wrote:
SUSE 10.1, KDE 3.5.2 updates.
Looking for confirmation that I have found an issue with YaST's Runlevel display.
I had to manually refresh the status of SuSEFirewall2 after stopping it and restarting it as part of setting up the ntp client. I received the desired 'Success [status 0]' message but I 'double-checked' before closing the module and it did /not/ show 'running' until I refreshed it.
Same problem here; 10.1 with the bundled KDE. The problem is many services that actually are running are indicated that they are not running in the Expert screen. Haven't yet found any services YaST shows as running that are not running. HTH. Mark -- _________________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine, LLC "We manage your network so you can manage your business" 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678 Web: http://www.rnome.com This email was sent from Reliable Networks of Maine LLC. It may contain information that is privileged and confidential. If you suspect that you were not intended to receive it, please delete it and notify us as soon as possible. Thank you.
On Friday 26 May 2006 2:58 pm, L. Mark Stone wrote:
On Fri, 2006-05-26 at 10:31 -0400, Carl Hartung wrote:
On Friday 26 May 2006 09:57, S Glasoe wrote:
SUSE 10.1, KDE 3.5.2 updates.
Looking for confirmation that I have found an issue with YaST's Runlevel display.
I had to manually refresh the status of SuSEFirewall2 after stopping it and restarting it as part of setting up the ntp client. I received the desired 'Success [status 0]' message but I 'double-checked' before closing the module and it did /not/ show 'running' until I refreshed it.
Same problem here; 10.1 with the bundled KDE. The problem is many services that actually are running are indicated that they are not running in the Expert screen. Haven't yet found any services YaST shows as running that are not running. HTH.
Mark
https://bugzilla.novell.com/show_bug.cgi?id=181607 if you'd like to add anything or vote on it... Thanks, Stan -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Tue, 2006-06-06 at 12:27 -0500, S Glasoe wrote:
On Friday 26 May 2006 2:58 pm, L. Mark Stone wrote:
On Fri, 2006-05-26 at 10:31 -0400, Carl Hartung wrote:
On Friday 26 May 2006 09:57, S Glasoe wrote:
SUSE 10.1, KDE 3.5.2 updates.
Looking for confirmation that I have found an issue with YaST's Runlevel display.
I had to manually refresh the status of SuSEFirewall2 after stopping it and restarting it as part of setting up the ntp client. I received the desired 'Success [status 0]' message but I 'double-checked' before closing the module and it did /not/ show 'running' until I refreshed it.
Same problem here; 10.1 with the bundled KDE. The problem is many services that actually are running are indicated that they are not running in the Expert screen. Haven't yet found any services YaST shows as running that are not running. HTH.
Mark
https://bugzilla.novell.com/show_bug.cgi?id=181607 if you'd like to add anything or vote on it...
Hi Stan, Good idea, I voted. Mark -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Tuesday 06 June 2006 1:00 pm, L. Mark Stone wrote:
On Tue, 2006-06-06 at 12:27 -0500, S Glasoe wrote:
https://bugzilla.novell.com/show_bug.cgi?id=181607 if you'd like to add anything or vote on it...
Hi Stan,
Good idea, I voted.
Mark
Just an update that my bug report is a duplicate to #173418. That is for SLES 10 and is not viewable/searchable publicly so I wouldn't have known it existed. Proves I searched bugzilla.novell.com first though! Better news is that it has been fixed in yast2-runlevel-2.13.8. Don't know when that'll get released. Stan -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (3)
-
Carl Hartung -
L. Mark Stone -
S Glasoe