pe un debian etch: mumu:~# ls -l /etc/rc2.d/ /etc/rc0.d/ |grep mysql lrwxrwxrwx 1 root root 19 2007-01-24 21:53 K20mysql-ndb -> ../init.d/mysql-ndb lrwxrwxrwx 1 root root 15 2007-01-24 21:53 K21mysql -> ../init.d/mysql lrwxrwxrwx 1 root root 23 2007-01-24 21:53 K21mysql-ndb-mgm -> ../init.d/mysql-ndb-mgm lrwxrwxrwx 1 root root 15 2007-01-24 21:53 S19mysql -> ../init.d/mysql lrwxrwxrwx 1 root root 23 2007-01-24 21:53 S19mysql-ndb-mgm -> ../init.d/mysql-ndb-mgm lrwxrwxrwx 1 root root 19 2007-01-24 21:53 S20mysql-ndb -> ../init.d/mysql-ndb
mumu:~# ls -l /etc/rc2.d/ /etc/rc0.d/ |grep free lrwxrwxrwx 1 root root 20 2007-01-27 11:22 K50freeradius -> ../init.d/freeradius lrwxrwxrwx 1 root root 20 2007-01-27 11:22 S50freeradius -> ../init.d/freeradius In cazul in care am freeradius cu userii tinuti in mysql si dau shutdown la server, mysql se opreste inainte lui freeradius si astfel freeradius nu apuca sa inchida sesiunile userilor din mysql. Aceasi ordine am vazut ca este si in "Sarge" care e stable. Mi se pare totusi o eroare prea evidenta si am zis sa intreb inainte sa ma apuc eu sa modific ordinea la shutdown. So, e bug sau asa trebuie sa fie si nu imi dau eu seama ? Am verificat si in fedora si acolo ordinea pare ok, adica radius e oprit inaintea lui mysql. _______________________________________________ RLUG mailing list [email protected] http://lists.lug.ro/mailman/listinfo/rlug
