On 4/10/2013 2:04 PM, Cristian Rodríguez wrote:
El 10/04/13 17:57, Marc Chamberlin escribió:
Is the only workaround, to automatically starting up services during boot up, is to go in and manually create the links in the /etc/init.d/rc*.d directories for the various services one needs?
huh ? what makes you think that is a solution ? Wow, had no idea I was going to create such a firestorm of replies!!!
Why do I think this is a solution? Because one of the replies (Comment #8) in Bug #800514 implied that it might be. And I tried it for the dhcpd service and it worked... Then I realized that this was going to be a difficult workaround approach when it came to trying to figure out the order in which services need to be started and stopped (which is info that I discovered is embedded in the names of the links in the various rc*.d directories...) Hence I asked and stated what I had tried....
to start service on boot
systemctl enable yourservice
Thanks, I will give that a try again... I actually did see this command mentioned in Bug #800514 and gave it a shot on one of our services, and it failed for some reason. I will try to revisit it and see if I can recreate it, (I think it was for named) but it may have been an interaction with the other bug I mentioned about supporting dual NICs on a gateway. Not being familiar with this command, or systemd in general, I set it aside and continued to try an grok the situation and look for other solutions.
it is that simple, and works.
The learning curve is sometimes very steep and there are lots of "magic" commands that not everyone is familiar with. That is why having good GUI's, that act as guides to help us poor uneducated users solve such problems, is so important. IMHO! Then we wouldn't have to bother the experts with our dumb questions. Having a sea of command line commands with a universe of options is wonderful for all the advance Linux gurus in the world, but for those of us who are learning the ropes, it is not always easy to find these golden nuggets on our own or discover/grok a new command such as systemctl.... Please do not assume that someone who is asking questions and struggling with his/her system is as knowledgeable about the subject, as you are...
yast modules will probably be revamped/improved when converted to Ruby from YCP, that might take a while.
As there are only a handful of souls that speak the YCP language and some of them even no longer work for SUSE..yast needs such conversion in order to survive.
I look forward to the day when a new GUI presents itself in the openSuSE world. In the meantime, don't be surprised if/when I ask "dumb" questions on how to do something that YaST was once able to do for me. Getting openSuSE12.3 up an running has become a frustrating experience for us. Our servers and gateway systems were running under 11.4 for a long time, but with some growing discomfort, so we decided it was time to try an upgrade... It has NOT proven to be an easy transition... Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org