[Bug 384401] New: SCR does not clean up when yast is loaded from perl
https://bugzilla.novell.com/show_bug.cgi?id=384401 User mvidner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=384401#c350581 Summary: SCR does not clean up when yast is loaded from perl Product: openSUSE 11.0 Version: Beta 1 Platform: All OS/Version: openSUSE 11.0 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: mvidner@novell.com ReportedBy: mvidner@novell.com QAContact: jsrain@novell.com CC: rhafer@novell.com Found By: Development +++ This bug was initially created as a clone of Bug #350581 +++ When trying to debug that bug, we discovered that SCR may neglect to write pending changes in certain cases. See bug 350581 comment 6. However, these conditions do not occur when yast is used normally, therefore I mark it as Minor. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=384401
User rhafer@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384401#c1
Ralf Haferkamp
+++ This bug was initially created as a clone of Bug #350581 +++ However, these conditions do not occur when yast is used normally, therefore > I mark it as Minor. Hm, then I must be using YaST "unnormally" :). I run into exactly this problem, while working on a feature in yast2-ldap-server. While writing out the configuration I first call:
SCR->Write('.sysconfig.openldap.OPENLDAP_START_LDAPI', 'yes'); and shortly after that I restart the LDAP server with: Service->Restart("ldap"); The above sysconfig setting is used by the openldap's init-script to determine the interface that the server should be listening on. As the change as not been written to the file upon the Service->Restart() call, the service is not started correctly, i.e. in this case the LDAPI listner ist not enabled. Please clarify why this use of YaST is not normal. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=384401
User mvidner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384401#c2
--- Comment #2 from Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=384401
User rhafer@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384401#c3
--- Comment #3 from Ralf Haferkamp
https://bugzilla.novell.com/show_bug.cgi?id=384401
User mvidner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384401#c4
--- Comment #4 from Martin Vidner
It is bad design, in that the cost of the benefit (the caching) is a big surprise for the programmer. Yes that is a pretty big tradeoff. I am not sure how big the benefit is,
https://bugzilla.novell.com/show_bug.cgi?id=384401
User rhafer@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=384401#c5
--- Comment #5 from Ralf Haferkamp
I will think about how to disable it by default in the next release. Good :)
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com