[opensuse] YaST Services Manager in 13.1?
I've just upgraded from 12.3 to 13.1, and have run into something that's... odd. It's almost certainly me missing the obvious, but... since I'm missing it... I've installed ddclient and created my usual ddclient.conf file. In previous releases I'd pop open YaST and go to the Runlevel Editor and enable ddclient. In 13.1, the Runlevel Editor is gone, replaced with the Services Manager. The Services Manager is nice, and an improvement over the old tool.. but... I don't see my ddclient Service in the list. Other things I've installed like Apache are there and I can enable/manage nicely. If I use chkconfig, I see this: ------------------ ddclient off ------------------ Which is to be expected since I haven't manually started the service. So... am I looking in the wrong place in YaST to enable the service? I could do it CLI, but... I'm looking for the GUI way to do this and sort of expected to just find it there in the new Services Manager. C. -- openSUSE 13.1 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Dec 6, 2013 at 9:26 PM, C wrote:
I've just upgraded from 12.3 to 13.1, and have run into something that's... odd. It's almost certainly me missing the obvious, but... since I'm missing it...
I've installed ddclient and created my usual ddclient.conf file. In previous releases I'd pop open YaST and go to the Runlevel Editor and enable ddclient. In 13.1, the Runlevel Editor is gone, replaced with the Services Manager.
The Services Manager is nice, and an improvement over the old tool.. but... I don't see my ddclient Service in the list. Other things I've installed like Apache are there and I can enable/manage nicely.
If I use chkconfig, I see this: ------------------ ddclient off ------------------
Which is to be expected since I haven't manually started the service.
So... am I looking in the wrong place in YaST to enable the service? I could do it CLI, but... I'm looking for the GUI way to do this and sort of expected to just find it there in the new Services Manager.
I take it that no one really knows then? I'm able to start the service using the old fashioned chkconfig ddclient on, but... I'd still like to know why can't I do the same through YaST Services Manager. Have I stumbled onto a bug in the new YaST component? Or is it me being a numpty (the usual thing)? C. -- openSUSE 13.1 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-12-07 08:45, C wrote:
I take it that no one really knows then?
I'm able to start the service using the old fashioned chkconfig ddclient on, but... I'd still like to know why can't I do the same through YaST Services Manager. Have I stumbled onto a bug in the new YaST component? Or is it me being a numpty (the usual thing)?
There is a known bug about that, corrected in an update. Do you have all of them? (zypper patch or yast online update). -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
On Sat, Dec 7, 2013 at 4:19 PM, Carlos E. R. wrote:
On 2013-12-07 08:45, C wrote:
I take it that no one really knows then?
I'm able to start the service using the old fashioned chkconfig ddclient on, but... I'd still like to know why can't I do the same through YaST Services Manager. Have I stumbled onto a bug in the new YaST component? Or is it me being a numpty (the usual thing)?
There is a known bug about that, corrected in an update. Do you have all of them? (zypper patch or yast online update).
I've poked bugzilla a bit, but the only thing I've found is a few comments about people not liking systemd and how many programs can't talk to systemd yet. I guess ddclient falls under that category of not talking to systemd. Yes, my 13.1 install is fully updated. Oh well... I can (and have) start it with chkconfig. It's a one time thing, and then I ignore it. C. -- openSUSE 13.1 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-12-07 16:42, C wrote:
Oh well... I can (and have) start it with chkconfig. It's a one time thing, and then I ignore it.
Open a bugzilla or it will be there fore ever. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
On Friday 06 Dec 2013 21:26:07 C wrote:
I've just upgraded from 12.3 to 13.1, and have run into something that's... odd. It's almost certainly me missing the obvious, but... since I'm missing it...
I've installed ddclient and created my usual ddclient.conf file. In previous releases I'd pop open YaST and go to the Runlevel Editor and enable ddclient. In 13.1, the Runlevel Editor is gone, replaced with the Services Manager.
The Services Manager is nice, and an improvement over the old tool.. but... I don't see my ddclient Service in the list. Other things I've installed like Apache are there and I can enable/manage nicely.
If I use chkconfig, I see this: ------------------ ddclient off ------------------
Which is to be expected since I haven't manually started the service.
So... am I looking in the wrong place in YaST to enable the service? I could do it CLI, but... I'm looking for the GUI way to do this and sort of expected to just find it there in the new Services Manager.
C. Hasn't Yast been rewritten in Ruby for 13.1? if so, maybe not all functionality is yet present -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Dec 7, 2013 at 12:38 PM, ianseeks wrote:
On Friday 06 Dec 2013 21:26:07 C wrote:
I've just upgraded from 12.3 to 13.1, and have run into something that's... odd. It's almost certainly me missing the obvious, but... since I'm missing it...
I've installed ddclient and created my usual ddclient.conf file. In previous releases I'd pop open YaST and go to the Runlevel Editor and enable ddclient. In 13.1, the Runlevel Editor is gone, replaced with the Services Manager.
The Services Manager is nice, and an improvement over the old tool.. but... I don't see my ddclient Service in the list. Other things I've installed like Apache are there and I can enable/manage nicely.
If I use chkconfig, I see this: ------------------ ddclient off ------------------
Which is to be expected since I haven't manually started the service.
So... am I looking in the wrong place in YaST to enable the service? I could do it CLI, but... I'm looking for the GUI way to do this and sort of expected to just find it there in the new Services Manager.
C. Hasn't Yast been rewritten in Ruby for 13.1? if so, maybe not all functionality is yet present
Services Manager is a new component in YaST for 13.1. It sees loads of other servicesa dn works just fine for enabling something like say.. apache, just not this ddclient service.. I can/have enabled it using chkconfig. That I can do, but... Like I said, I expected Services Manager to show ddclient, and it's not there. I've poked at it with systemcfg as well, and can't see the service there... it ONLY shows up with chkconfig. I don't knwo enough about this level (yet?) to dig around intelligently and find out... is it something in ddclient that's missing? Is it something in systemd? Or a but in YaST? I could raise a bug report, but... one what component? with what information? C -- openSUSE 13.1 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 07/12/2013 13:10, C a écrit :
I've poked at it with systemcfg as well, and can't see the service there... it ONLY shows up with chkconfig.
looks like an old init not yet ported to systemd
but in YaST? I could raise a bug report, but... one what component? with what information?
search for ddclient in bugzilla, if nothing go to systemd component jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Dec 7, 2013 at 6:38 AM, ianseeks <ianseeks@yahoo.co.uk> wrote:
Hasn't Yast been rewritten in Ruby for 13.1? if so, maybe not all functionality is yet present
Rewritten implies manual work. That's not what happened. They wrote a language translator. The translator took all the old code and converted it to Ruby. During devel, they just kept fixing the translator and kept rerunning it and testing the result. In the end, all of the old yast modules that were going to be translated were translated. There is no "not translated yet" work left. Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday 07 Dec 2013 09:59:52 Greg Freemyer wrote:
On Sat, Dec 7, 2013 at 6:38 AM, ianseeks <ianseeks@yahoo.co.uk> wrote:
Hasn't Yast been rewritten in Ruby for 13.1? if so, maybe not all functionality is yet present
Rewritten implies manual work. That's not what happened.
They wrote a language translator. The translator took all the old code and converted it to Ruby.
During devel, they just kept fixing the translator and kept rerunning it and testing the result.
In the end, all of the old yast modules that were going to be translated were translated. There is no "not translated yet" work left.
Greg
-- Greg Freemyer
thanks for the explanation -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
C -
Carlos E. R. -
Greg Freemyer -
ianseeks -
jdd