Description of problem: Version-Release number of selected component (if applicable): None at install How reproducible: Install fresh system of Mageia v5.1 ISO -> DVD (in this case on a SSD) Steps to Reproduce: 1. Do install. xinetd not installed by default and leafnode is not installed by request as not needed. Only found when a service was not running.
Well, the intention is to let systemd handle all services. In many cases that is enough, and installing xinetd is not needed > leafnode is not installed by request as not needed. I don't understand your remark about leafnode :-( Did you deselect it during install? leafnode is one of the few packages that still require xinetd
Keywords: (none) => NEEDINFOCC: (none) => marja11
Nothing was deselected - did not even know you could. Install was right out of the box on a clean partition UEFI SSD. Then I reloaded the /home -> hard drive alogn with one other into another directory off /home/ user Then starting installing required packages via mcc and it was only after a reboot and looking at why my BBS system was not running that I found that the xinetd was not present (xinedt.conf). Some one else pointed out that leafnode is tied with it and suggested if I had uninstalled it then xinetd joined it but that was not the case - I did not manually install neafnode and as far as I know it still has not been installed. Nope just checked .
Doe your BBS system (bulletin board service, I suppose?) need xinetd, or can systemd handle it? which BBS package(s) did you install?
Back ground first - I used mga 5.1 to help build a new SSD that had partitions prebuilt along with Win 10 - Don't ask!. Having installed it I mounted my hard drive to it at /home so all user data along with the bbs data/programs is present and this was the set up on the old SSD that always run out of space despite being only lightly used . Due to poor compat? with fstrim. The BBS is mbse which is a Linux based only system (on SF) as mbsebbs) so I had some installs to do and then run systemctl or /etc/rc.d/in/mbsed start - however it failed and it was only when looking at my xinetd.d/mbsebbs settings that I noticed that there was no xinetd.conf file present and then found no os/w was installed. Once that was sorted the BBS came up and working (after I had removed the firewall settings) as that is dealt with further upstream. The xinetd is needed or failing that inetd function which is what happened with Mga v4 and Mandriva before it. System has been is use with Mga v4 & 5 for some years. I do NOT update to the latest distro until it has been out > 10+ weeks so that more bugs are removed as I have enough problems even now with v5.1 and mariadb and mysql-workbench not talking and that one was reported almost 2 years ago. .
Mageia 5 still has xinetd, just like versions before it. It's not going to automatically install xinetd unless you also install a service that uses it. As Marja already pointed out, most services that used to use xinetd no longer do, as they use systemd socket units now. If you're installing some custom software that you know needs xinetd, then you need to install xinetd.
Status: NEW => RESOLVEDResolution: (none) => INVALID
Thank you for the help - my problem is that mbse the bbs s/w does not know about using systemd it only suppplies a script for putting into /etc//rc.d/init.d/ The script is nothing special but I have no knowledge of how to covert it and install it for systemd to function instead. For your interest I am including the script here : ---- #!/bin/sh # # chkconfig: 345 95 05 # description: Starts and stops MBSE BBS. # # For RedHat, Fedora Core, E-Smith and Mandrake SYSV init style. # $Id: init.RedHat,v 1.9 2007/07/09 18:46:51 mbse Exp $ # # Source function library. . /etc/rc.d/init.d/functions # Source networking configuration. . /etc/sysconfig/network # Check that networking is up. [ ${NETWORKING} = "no" ] && exit 1 # Find the MBSE_ROOT from the /etc/passwd file. MBSE_ROOT=`cat /etc/passwd | grep ^mbse: | awk -F ':' '{ print $6}'` if [ "${MBSE_ROOT}" = "" ] then echo "MBSE BBS: No 'mbse' user in the password file." exit 1 fi if [ ! -d ${MBSE_ROOT} ] then echo "MBSE BBS: Home directory '${MBSE_ROOT}' not found." exit 1 fi export MBSE_ROOT # See how we were called. # case "$1" in start) echo -n "Starting MBSE BBS: " rm -f ${MBSE_ROOT}/var/run/* rm -f ${MBSE_ROOT}/var/sema/* rm -f ${MBSE_ROOT}/var/*.LCK rm -f ${MBSE_ROOT}/tmp/mb* su - mbse -c '${MBSE_ROOT}/bin/mbtask' >/dev/null echo -n "mbtask " sleep 2 if [ -f ${MBSE_ROOT}/etc/config.data ]; then su - mbse -c '${MBSE_ROOT}/bin/mbstat open -quiet' echo "opened" fi touch /var/lock/subsys/mbsed ;; stop) echo -n "Shutting down MBSE BBS: " if [ -f ${MBSE_ROOT}/var/run/mbtask ]; then echo -n "logoff users " su - mbse -c '${MBSE_ROOT}/bin/mbstat close wait -quiet' >/dev/null echo -n "done, " echo -n "stop mbtask: " killproc mbtask -15 rm -f /var/lock/subsys/mbsed sleep 3 fi echo "" ;; status) status mbtask ;; restart|reload) $0 stop $0 start ;; *) echo "Usage: $0 {start|stop|restart|reload|status}" exit 1 esac exit 0 ---- Note that the bbs runs at a root level within it's own user account as it needs to go into passwd when setting up an internal new user as well as a Linux user. Not that that works since v5 as all attempts to change the linux passwd results in a passwd file is busy - even when I change the setting of it to 777 having disconnected internet links, as a very quick test that also failed and yes I reverted back to the original setting immediately after. I have since stopped any new users logging into the BBS.
I don't see any references to xinetd in that script, and typically xinetd services *don't* use their own /etc/rc.d/init.d script, they just install a file into /etc/xinetd.d. Either way, SysV and xinetd services don't *have* to be converted to systemd units, as systemd supports SysV init scripts (the ones in /etc/rc.d/init.d) and you can still run xinetd, so your software should still work.