[SOLVED] cussing systemd - any way to get rid of it?

[RahulSundaram]

Hi


chkconfig and service commands automatically call the systemctl equivalents when needed and hence both are "proper" tools. There is nothing whatsoever wrong with using them. Full switch to systemd is already done for all intend and purposes. chkconfig and service command will be available for the foreseeable future. it is not like it is high maintenance or anything.

systemctl start NetworkManager.service is not that different from service NetworkManager start and systemctl disable Networkmanager.service is not that different from chkconfig NetworkManager off and yes, it is a few keystrokes more but you are exaggerating about the impact especially since the older equivalent will continue to work fine.. systemd manages more than just services and hence the explicit names and this is by design so that the mapping is straight forward.

systemadm as noted in the wiki is work in progress and hence not installed by default. Don't use it unless you are a developer.

[DBelton]

it was installed by default on my system when I did a F15 install. I didn't even know what it was until after teh F15 install and it was there.

[RahulSundaram]

Hi

That is pretty unlikely since I don't see it specified in kickstart or comps as default. Run grep systemd-gtk in /var/log/yum.log and /root/anaconda-ks.cfg to figure out how it got installed. I definitely had to install it manually.

[DBelton]

it must have been during the install when I did the customize installation stuff, then.

It shows up in /var/log/yum.log but I know I didn't install it after the initial install. It was there on my first boot.

I guess I need to pay more attention to what I check when I customize my installation

Actually, I would have installed it even if I had known what it was, because the entire reason I installed F15 was to try out the new things and see where fedora is heading. This install will be completely wiped out and a fresh install done later when I get things all (or at least somewhat) figured out so I can change the things I want without having bad things laying around to mess things up.

There are a couple of things I'm going to be filing a bug report on as soon as I can pin down a little more information (like yum looping when I use --skip-broken) but overall, I haven't completely trashed my system yet, so that's a good sign for F15

[vallimar]

I've been using systemd for awhile, and have put up with its bugginess for some time but
when your system gets hosed just trying to toggle a service, that's too much. Let me know
when that gets fixed and I'll consider switching back.

DBelton, if you haven't installed bash-completion yet, do so. Systemd comes with a completion
script so you can tab-complete most things to save on typing. Works for 'service' and many
other commands too. Why this isn't installed by default with bash is a mystery. You will want
to relog into any open console sessions, or manually source it. Keep in mind that if you make
later changes, it's designed so you cannot update it later without a relog once it's been loaded
into a terminal session.

Something I discovered digging around, if you do choose the upstart fallback method, but want
to keep the later chkconfig versions, you need to either use --no-redirect or set a ENV variable
SYSTEMCTL_SKIP_REDIRECT=1 to have it always on. This is so you can manipulate the init.d
service files instead of the systemd ones. When trying to enable/disable services, it does not
check if systemd is active, just blindly forwards to systemctl which fails if it isn't.

[RahulSundaram]

Hi
He has been suggested atleast two different ways of doing it and he has confirmed that one works and closed the bug report he filed. For those not following along, a quick rehash

graphical target is defined as multi-user target + X and if one wants to enable a service to start by default on the command line but not start it on the graphical target, the simplest way is to enable the service on multi-user target and just run

ln -s /dev/null /etc/systemd/system/graphical.target.wants/foo.service

This will ensure that the service won't start in the graphical target. You can also define a custom target that does what you want to do but that isn't necessary in this case.

[DBelton]

yes, you are correct, Rahul. There are several ways to accomplish what I was originally asking about, and the way you show above works rather nicely

I will admit that most of my problems with systemd, you cleared up for me. I had thought that it was installed by default on my machine and while I don't mind development code, I want it to be by my choice, and not something I thought was supposedly closer to being a finished product.

Once you showed me that I had installed it (during customizing my install) then quite a lot of things settled down in my old brain

I will say that systemd does do a pretty good job from what I have seen so far once you get used to the extra verbosity involved.

Most complaints will probably be that it does things different than SysV/upstart (that can be both good and bad) and takes a learning curve, but once you figure it out, it's not that hard. Some things are actually easier than with upstart.

Now.. Gnome 3 shell.. well.. that one is a totally different matter.. I'd love to plant a bomb under that code and blow it all to heck and back. LOL