![](https://seccdn.libravatar.org/avatar/6167b5e19c9699446f8122d902491a63.jpg?s=120&d=mm&r=g)
On Tuesday 24 October 2006 07:07, C. Brouerius van Nidek wrote:
Learned in the past weeks that it is necessary to run SuSEconfig after using Smart. During my DOS days I would have made a batfile where Smart would be followed by SuSEconfig. Could that be done easily in Suse 10.1?
I've edited my KDE menu entry for Smart GUI to be: smart --gui && ldconfig && SuSEconfig That way when I exit smart I know that ldconfig and SuSEconfig are run. There aren't any visual or audio notifications of success (failure may pop up a text window with errors?). htop shows the processes running. The HDD activity LEDs light up. Wait a few minutes for it to finish... You can also run ldconfig && SuSEconfig in a konsole, as root, while smart is idle. I do this if there are lots of KDE updates as well as others and am getting repository errors or slow Internet or dependency issues, etc.
What wonders me is the instruction in one of the email's to use "ldconfig && SuSEconfig" From the short timespan I used Red Hat (RH 5.2) I remember ldconfig but since my happy Suse years I can't remember using ldconfig. What is the background of the combined instruction? Ldconfig does not do anything visual on my system. SuSEconfig does ;).
Linux User 183145
Carl is correct that YaST Software Install runs ldconfig prior to running SuSEconfig as part of its normal process whenever you add/remove software. Synaptic for SUSE also did this after every add/remove software session. Smart may do this with openSUSE sometime in the future. I believe the smart developer(s) are aware of this need for SUSE. Stan