ok, this isnt really a virtualmin question, or maybe it is im not sure.
I have two fedora 5 boxes, and on the one I can issue
service xinetd restart
to restart the xinetd service
on the box with virtualmin installed, I get unrecognized service, All I want to do is start rsync as a daemon, which I made the needed changes under the xinetd directory and now I need to start it like after a reboot. I know rebooting would work, but I cant figure out what I am doing wrong here and restarting would be lame just because I cant figure out what I am doing wrong.
both machines installed from same install cd’s, and I thought I had installed them to be as identical as possible.
Does the installation of virtualmin pro change whether or not xinetd is running?
Nope, we don’t touch xinetd. We don’t use it for any of our services, and so our install.sh and virtualmin-base package never even look at it.
I’m not sure what would make xinetd go away…You could check to be sure it is installed:
rpm -q xinetd
And then be sure the package files haven’t been modified:
rpm -V xinetd
The file that "service" uses would be /etc/init.d/xinetd
I looked inside the /etc/init.d/ folder and couldnt find xinetd.
So I checked and it shows that it is not installed.
So to start webmin and virtualmin when the computer boots, how is that done Since this computer doesnt have xinetd installed? Do you just put the startup script inside the init.d folder and it starts it as a service?
I dont know why xinetd is not installed, I thought it was default on fedora packages, maybe I am loosing my mind:0
I suspect you’re thinking of the initscripts and chkconfig and init packages. Those are the packages that manage the boot sequence on your system.
xinetd is a generic server daemon, that allows some service to be started automatically when a connection is made on the appropriate port. It is sometimes used for telnet and FTP and web, but not usually (and not preferably in the case of FTP or web, since it makes it slower to connect for users–and many FTP and web servers no longer support starting up that way). As I mentioned, we don’t use it for any of our services, so we don’t touch it. We don’t install it or configure it. I can’t think of anything you’d need it for on a web hosting box, but there might be something special in your environment.
To cause a properly designed initscript to be started on boot, you use chkconfig (or the Webmin Bootup and Shutdown module), for example:
chkconfig --level 345 postfix on
Which will cause the postfix service to start on boot in runlevels 3, 4, and 5 (3 is the normal command line environment, 5 is the normal X environment, and 4 can be used for whatever special environment you want to design…but realistically no one ever uses it for anything).
xinetd is not part of the normal Fedora installation unless you install something that needs it.
Hope this helps explain it all.