This is an fyi, rather than a question, as I’ve resolved the issue (to my satisfaction), as detailed here:
http://suseunbound.forum-free.ca/t394-systemd-missing-targets-in-yast#2360
Item #1: The openSUSE doc page for systemd contains a significant error. I sent a message earlier today to openSUSE noting this. The page lists two directories for targets: /etc/systemd/system, and /lib/systemd/system. That 2nd directory SHOULD read /usr/lib/systemd/system. At least, this is true for openSUSE 13.1. (and as of this date: Thu Apr-24-2014. I would expect the page should get fixed quickly.)
Item #2: The Yast Services Manager module does not yield a complete list of available targets in the options for default target. At least, not in the ncurses version. I verified this using
systemctl list-units --type target
This command showed me the targets I would expect (multi-user, etc) that did not show up in the Yast Services Manager “default system target” drop-down box. I have NOT reported this as a bug yet - but I need to do so. Unless - somebody points out that I am completely wrong because I did some idiot move somewhere!
So, IF you run into problems figuring out the systemd targets, try these pages to help:
7.3. Working with systemd Targets
Chapter 8. The systemd Daemon | ActiveDoc
RH Systemd - Crashcourse Wiki
On 2014-04-24 22:26, spokesinger wrote:
> Item #1: The ‘openSUSE doc page for systemd’
> (http://tinyurl.com/l3gmqdt) contains a significant error. I sent a
> message earlier today to openSUSE noting this.
A message? Like an email?
You have to communicate issues via Bugzilla. If you send emails they
will probably be ignored.
openSUSE:Submitting bug
reports
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Re: systemd doc error
I sent an email via the “contact us” utility - for the doc error. Already got a reply - so that DID work - and not an auto-reply. Reply was “you can edit this yourself, you know.” Very polite tho and offered to do it for me.
However, I have no idea if the location error I noted in the doc WAS true in a prior release (since the two machines I’m running have 13.1+)
If someone out there will confirm that the noted target files are located in usr/lib/systemd/system in prior releases (when did openSUSE start using systemd?) - I’ll make the page edit.
So - if anyone will validate that they recognize this is an error - and has been for prior releases - I’ll fix it.
Re: yast bug
THIS issue I reported via bugzilla after I posted the op.
Upto (and including) 12.2, /lib/systemd/system is used, starting with 12.3 this was moved to /usr/lib/systemd/system.
The first openSUSE release containing systemd as default was 12.1.
Re: yast bug
THIS issue I reported via bugzilla after I posted the op.
I cannot really reproduce this.
multi-user.target is shown here in YaST->Services Manager.
Of course not all targets are shown that “systemctl list-units --type target” lists.
Specifically, those that don’t contain “AllowIsolate=yes” are not shown here. But I suppose that’s on purpose, as you cannot boot to them.
From the ones with “AllowIsolate=yes”, only those are missing:
- default.target: I think it’s obvious why
- initrd-switch-root.target, initrd.target, system-update.target, emergency.target: that those are not listed, doesn’t really sound like a bug to me.
FYI, here’s a screenshot:
http://wstaw.org/m/2014/04/25/yast.png
I take it that your missing targets are listed by “systemctl”?
Maybe your missing targets are masked in /etc/systemd/system (i.e. symlinked to /dev/null)?
I can reproduce your description by doing that. (i.e. targets are shown with systemctl, but not in YaST)
But that wouldn’t be a bug either IMHO. By symlinking to /dev/null you effectively disable a unit/target, so it makes sense that YaST doesn’t show it I’d say.
On 2014-04-25 20:06, spokesinger wrote:
>
> Re: systemd doc error
> I sent an email via the “contact us” utility - for the doc error.
> Already got a reply - so that DID work - and not an auto-reply. Reply
> was “you can edit this yourself, you know.” Very polite tho and offered
> to do it for me.
Oh. That’s a recent change of policy.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
wolfi;
excellent reply, loads of detail. TY for the /lib /usr/lib location change. I can edit the doc with a footnote on the change.
On the yast bug - all what you say could be. I’ll have to play around later and see. Personally, I’m inclined to think it has something to do with the ARM image and how that was setup, rather than a real bug. But as for the operating details you’ve just provided? Brand new knowledge for moi. Actually, the whole systemd innards is brand-new knowledge for me. Hehe.
BUT, since I couldn’t explain the behavior, and couldn’t find any forum discussion of same, better to let somebody know and take a look. After spending way more hours than I had available to resolve the issue enough to move forward . . .
Cheers, and thanks.