On 5/22/08, Travis Willard wrote:

On Thu, May 22, 2008 at 11:07 AM, Nigel Henry wrote:

...

On my Fedora installs there is a GUI for stopping and starting services, and also the option of using chkconfig on the CLI. On my Debian installs, I installed sysv-rc-conf, which runs on the CLI, and allows you to stop and start services.

Is there anything similar that I could use on my Archlinux install?

Thanks for any help.

I can't recall any such tool offhand, though the discussion certainly has come up before. What's wrong with /etc/rc.d/service stop and /etc/rc.d/service start?

I would have to side with Travis here. In case it's just too much hassle to type, you can always add some bash functions to make it even simpler. Here's what I've got in ~/.bashrc (it's based off someone else's example from the forums...): # start, stop, restart, reload - simple daemon management # usage: start <daemon-name> start() { for arg in $*; do sudo /etc/rc.d/$arg start done } stop() { for arg in $*; do sudo /etc/rc.d/$arg stop done } restart() { for arg in $*; do sudo /etc/rc.d/$arg restart done } reload() { for arg in $*; do sudo /etc/rc.d/$arg reload done }

On Thu, May 22, 2008 at 09:09:50AM -0700, Thayer Williams wrote:

...

I can't recall any such tool offhand, though the discussion certainly has come up before. What's wrong with /etc/rc.d/service stop and /etc/rc.d/service start?

# start, stop, restart, reload - simple daemon management # usage: start <daemon-name> start() {

(The rest snipped for brevity). I just wanted to thank you for that one, I can't believe I'd never thought of doing it for any of my installs (including BSD and the RH based ones that use /etc/init.d). With slight modification, it will work for anything . Thanks again. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Xander: How could you let her go? Giles: As the soon-to-be-purple area on my jaw will attest, I did not 'let' her go.

Thayer Williams wrote:

On 5/22/08, Travis Willard wrote:

...

On Thu, May 22, 2008 at 11:07 AM, Nigel Henry wrote:

...

On my Fedora installs there is a GUI for stopping and starting services, and also the option of using chkconfig on the CLI. On my Debian installs, I installed sysv-rc-conf, which runs on the CLI, and allows you to stop and start services.

Is there anything similar that I could use on my Archlinux install?

Thanks for any help.

I can't recall any such tool offhand, though the discussion certainly has come up before. What's wrong with /etc/rc.d/service stop and /etc/rc.d/service start?

I would also have to agree - Arch keeps things so much more organized with the /etc/rc.d/service {start}{stop} rather than providing any tools for the user to possibly break. As for Gui tools, come on, Arch a 'simple, LIGHT weight' Linux distribution... If Arch had it's own GUI tools eventually it would need to pick a DE/WM as a default as well and then the bloat would come on. Arch is one of the few 'useful' Distro's left that has no real bloat to speak of, let's try to keep it that way.

On Thursday 22 May 2008 17:09, Travis Willard wrote:

On Thu, May 22, 2008 at 11:07 AM, Nigel Henry

wrote:

...

On my Fedora installs there is a GUI for stopping and starting services, and also the option of using chkconfig on the CLI. On my Debian installs, I installed sysv-rc-conf, which runs on the CLI, and allows you to stop and start services.

Is there anything similar that I could use on my Archlinux install?

Thanks for any help.

I can't recall any such tool offhand, though the discussion certainly has come up before. What's wrong with /etc/rc.d/service stop and /etc/rc.d/service start?

Johannes also suggests this way, and I have no problems with it, but sometimes it's just nice to have a list of running services, maybe just to see if there is some service you don't need, and to be able to stop it. A couple of suggestions on later posts have suggested packages available in AUR. I'll have a look at these. I was sort of thinking of new users, that may have been used to GUI stuff. A command on the CLI to bring up something using dialog, whiptail, or ncurses would also work, as you get a GUI of sorts. Also, sometimes it's not easy to know the name of a service. For example, you want to stop the ntp service. Do you stop ntp, or ntpd, and with ssh. Is this ssh, or sshd. I know you can try both, but a list of running services helps. This is just a little academic question so please don't be offended. All in all I'm very pleased with Archlinux (Don't Panic). I have a bunch of distros installed, Fedora, Debian, Kubuntu, Slackware, but none of them boot up as quick as my Archlinux install. Any suggestions as to what may be different from my other installs, that causes Archlinux to boot up so quickly? Nigel.

Excerpts from cave.dnb2m97pp's message of Thu May 22 12:21:16 -0500 2008:

Johannes also suggests this way, and I have no problems with it, but sometimes it's just nice to have a list of running services, maybe just to see if there is some service you don't need, and to be able to stop it.

"ls /var/run/daemons" will do. -- Jan

Excerpts from ert256's message of Thu May 22 10:18:48 -0500 2008:

I found that some time ago, but i don't use this. http://aur.archlinux.org/packages.php?ID=16966

This is not quite compatible with arch's initscripts. You'd need to rewrite (or at least rearrange) pretty much all the initscripts supplied with arch's packages, if you'd want to use this for the usual services. -- Jan

On Thu, 22 May 2008 20:15:39 +0200 Attila wrote:

On Donnerstag, 22. Mai 2008 17:07 Nigel Henry wrote:

...

On my Fedora installs there is a GUI for stopping and starting services, and also the option of using chkconfig on the CLI. On my Debian installs, I installed sysv-rc-conf, which runs on the CLI, and allows you to stop and start services.

I can understand your feelings because as i start using archlinux i search a tool as chkconfig too but i recognized that such a tool is not really necessary.

So why do i think this? The equipollent of "chkconfig --list | grep '3:on'" is the DAEMONS array in the rc.conf and the equipollent of the status of the running daemons ist the content of /var/run/daemons (kdm is not there but it have a pid file).

The only thing what i miss is that "chkconfig --list" shows me the x(inet) lines too but this is not so much necessary for archlinux from my view.

In my case i must say that the most what i have missed at the beginning has more to do with myself and what i have used before than with archlinux. Perhaps this helps you too.

See you, Attila

I've wrote a quick and dirty implementation of a tool for starting/stopping services and listing their status. It's quite simple tho, since it's just something I wrote to see if I remembered shell scripting...... http://arch.har-ikkje.net/scripts/daemon-0.5.sh

On Friday 23 May 2008 01:23, ndlarsen wrote:

Nigel Henry wrote:

...

On my Fedora installs there is a GUI for stopping and starting services, and also the option of using chkconfig on the CLI. On my Debian installs, I installed sysv-rc-conf, which runs on the CLI, and allows you to stop and start services.

Is there anything similar that I could use on my Archlinux install?

Thanks for any help.

Nigel.

Have a look at http://aldc.ionline.dk/ I havn't really had any time lately to work on it due to job overload, however, I do intend to pick it up again. Strictly CLI, though. Feedback will be appreciated.

Regards.

Hi Nicolas. Thanks for your aldc python programme. aldc list all shows all the running, and stopped services. I've only tried stopping, and starting vsftpd, while trying to ftp into the Archlinux machine from my FC2 install using gftp. The vsftpd service stopped ok, and could no longer access the archlinux machine using gftp. Then did aldc start vsftpd. gftp was still running, and retrying on the FC2 machine, and soon the directory list turned up in gftp on FC2. Your python program seems to be fine. it would be nice if it were more interactive, like the sysv-rc-conf program on Debian, but we can't have everything, and I'm willing to work with this. Thanks for your reply, and the program. Nigel.