How to utilize the Control Panel

[rms46]

Hello,
I am able to setup the sshd (openssh). However, I have no idea to turn it "on" or "off" by using the Control Panel. Do I miss something or any documentation/URL?

Rahmat.

[Juanito]

click on the desktop and use the "services" menu item to display the start/stop controls for daemons

[rms46]

click on the desktop and use the "services" menu item to display the start/stop controls for daemons

It does not work. I guess that there is a step that I have missed.

[curaga]

Is your sshd configured? Try starting "services" from a terminal and see if there are any messages toggling openssh.

[Lee]

I start openssh from within bootsync.sh with

Code: [Select]

/usr/local/etc/init.d/openssh startso I've never had occasion to start it from the services tool - I'd forgotten the tool was even there.

After reading the reply above I tried it out and found that, even though the ssh daemon is running, open ssh shows as off (no green light) on the services tool.  If I click the openssh button on the services tool, the green light comes on for a couple of seconds and goes out again.  The daemon remains running, still works and still has the same pid it had before.  This doesn't seem right to me but perhaps I'm just unfamiliar with the tool?

[gerald_clark]

I suspect the start fails as the port is already in use.  Try starting it with the daemon not running.

[Juanito]

The init.d script has to be written to interact with the services applet - see other extensions (for example bluez, dbus) for how this is done.

[Lee]

Thanks guys.  Both right.

The start failed, but it was because I had started the services tool from the command line, as user tc.  Without having examined the source code, I suspect cpanel starts the services tool as root, so services doesn't have to worry about explicitly starting the daemons as root.  When I started services as root, it worked a little better - but still no green light.

I did a quick compare of the openssh start/stop script, against the tftp start/stop script and found that the one for openssh lacks the "status" functionality (which simply reports the pid of the running daemon, if any).

After adding the status  functionality to the openssh script and running services as root, it appears to do work as expected.

[rms46]

(I am not sure if I should open a new thread or not)

What is the difference between /etc/init.d/ and
/usr/local/etc/init.d/ ?

There is a /etc/init.d/services/ directory for crond, tftpd, and dhcp.
Meanwhile openssh is in /usr/local/etc/init.d/

Rahmat.

[Juanito]

The idea is that the base uses /etc and extensions use /usr/local/etc

[rms46]

The idea is that the base uses /etc and extensions use /usr/local/etc

Does "services" checks /usr/local/etc or is it a bug?

[Juanito]

yes, services checks /usr/local/etc/init.d - bluez, dbus, cups, etc would not show otherwise 

[rms46]

Ah, yes. I have installed firefox which installs dbus.
Well then, to whom should I report the openssh problem?

[gerald_clark]

What makes you think it is a problem?

[rms46]

What makes you think it is a problem?

Openssh (sshd) can not be turned on/off by services.
That is not a problem? No problem!