Servers missing in Service Configuration GUI F17

teglis · #1 15th July 2012, 02:39 AM

I'm a long-time Fedora newbie, if there is such a thing. Prior to F17, I used Services on the Administration menu to launch a GUI that allows me to enable and disable services. However, with F17, dovecot, httpd and nmb/smb are missing from the dialog, even though they are installed. I'd really like to avoid the command line if possible. How do I get these servers to appear in Service Configuration?

Azhar · #2 15th July 2012, 07:56 AM

In terminal/command line issue the following command(s)

Code:

system-config-samba

Code:

system-config-httpd

it should bring up the appropriate service(s) in GUI environment.

#3 15th July 2012, 09:34 AM

Quote:

Originally Posted by teglis

I'm a long-time Fedora newbie, if there is such a thing. Prior to F17, I used Services on the Administration menu to launch a GUI that allows me to enable and disable services. However, with F17, dovecot, httpd and nmb/smb are missing from the dialog, even though they are installed. I'd really like to avoid the command line if possible. How do I get these servers to appear in Service Configuration?

You don't get a gui, try reading about systemctl

Code:

man systemctl

teglis · #4 15th July 2012, 02:22 PM

Thank-you both for your replies. Unfortunately it seems the solution is to do what I was trying to avoid: remember commands from one install to the next, rather than using an intuitive GUI. IMHO, Fedora has been getting increasingly hard (for a simple user) to set up in recent releases. I don't understand why it is evolving in this fashion.

Anyway, at least I have something to try; I do appreciate the quick response.

Thanks,
Rich

#5 15th July 2012, 02:37 PM

You could try systemd-gtk but it was broken last time I tested it.

Code:

su
yum install systemd-gtk

It's so broken (it's a breach of packaging guidelines not to have a menu entry for a gui app) they didn't bother giving it a menu entry so you would need to start it from command line.

Code:

systemdadm

oldbrad · #6 17th October 2012, 03:53 PM

Humm.. It's so broken that the command systemdadm does not exist. LOL Simplest solution is to revert to a pre systemd version. As far as I can see the only reason for systemd is fast startup. Who cares? Servers just run, fc6 is as stable as a rock and doesn't keep hassling for updates too.

I guess if you really want a GUI you'll have to build one. If you can get to the bottom of systemd that is.

***DBelton*** · #7 17th October 2012, 07:29 PM

try systemadm instead of systemdadm

The name changed.

Edit:

package name also changed as well:

yum install systemd-ui

oldbrad · #8 17th October 2012, 07:47 PM

Thanks I stand corrected.

Although systemd-gtk still exists. As Yellowman has observed that the package breaks the guidelines perhaps it should be removed.

In fact systemadm seems to be more capable than many of the posts on the net would have us believe.

***DBelton*** · #9 17th October 2012, 07:52 PM

I believe it has improved a little since this thread was started. It's not a priority for the developers, so it's coming along slowly, but I do think it has improved somewhat.

When it was first released, you couldn't do anything nut display the units. You couldn't stop a service, or anything.

Edit:

I was looking at the Fedora 18 packages when I noticed the name had been changed to systemd-ui. They probably kept the old name for older Fedora versions.