[Eisfair] [e1] reboot-Problem wegen xinetd

[Taxena Gasparov]

Am 15.01.21 um 11:45 schrieb Holger Bruenjes:
> wie sieht die Reihenfolge beim runterfahren aus
> ls  -1 /etc/rc2.d/K*

/etc/rc2.d/K00local
/etc/rc2.d/K01sane
/etc/rc2.d/K03eisfax
/etc/rc2.d/K10mini_httpd
/etc/rc2.d/K12hddtemp
/etc/rc2.d/K20capi2text
/etc/rc2.d/K20mdadm
/etc/rc2.d/K22asterisk
/etc/rc2.d/K23dahdi
/etc/rc2.d/K25sn
/etc/rc2.d/K27minidlna
/etc/rc2.d/K28smbfs
/etc/rc2.d/K30lprng
/etc/rc2.d/K30samba
/etc/rc2.d/K32capi
/etc/rc2.d/K35mail
/etc/rc2.d/K40apache
/etc/rc2.d/K40rsync
/etc/rc2.d/K41squid
/etc/rc2.d/K44brute_force_blocking
/etc/rc2.d/K45mariadb103
/etc/rc2.d/K45mariadb55
/etc/rc2.d/K47lm_sensors
/etc/rc2.d/K47talk
/etc/rc2.d/K48atd
/etc/rc2.d/K48cron
/etc/rc2.d/K49ssh
/etc/rc2.d/K50alsa
/etc/rc2.d/K50nginx
/etc/rc2.d/K50pure-ftpd
/etc/rc2.d/K50xinetd
/etc/rc2.d/K53nfsclient
/etc/rc2.d/K54nfsclient-shutdown
/etc/rc2.d/K55nfsserver
/etc/rc2.d/K55redis
/etc/rc2.d/K58ntp
/etc/rc2.d/K60dhcpd
/etc/rc2.d/K60syslogd
/etc/rc2.d/K63bind9
/etc/rc2.d/K64haveged
/etc/rc2.d/K65resolv
/etc/rc2.d/K68bonding
/etc/rc2.d/K69eisgraph_traffic_port
/etc/rc2.d/K69routing
/etc/rc2.d/K70route
/etc/rc2.d/K75ip-eth
/etc/rc2.d/K86usb
/etc/rc2.d/K87quota
/etc/rc2.d/K88lo
/etc/rc2.d/K89ide
/etc/rc2.d/K97udev
/etc/rc2.d/K99hostname
/etc/rc2.d/K99modules