https://qa.mandrakesoft.com/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2003-02-06 19:20 ------- [...] Upgrade to latest cooker linuxconf and initscripts ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: __UNKNOWN__ status: RESOLVED creation_date: description: Every time when I've finished with using linuxconf, it wants to perform some tasks before leaving (sorry it's in French :-): La commande suivante indique que quelque chose doit être fait /etc/rc3.d/S10network probe Execution de :/etc/rc3.d/S10network Utilisation : /etc/rc3.d/S10network {start|stop|restart|reload|status} La commande suivante indique que quelque chose doit être fait /etc/rc3.d/S14nfslock probe Execution de :/etc/rc3.d/S14nfslock restart [ ... and other things ... ] But /etc/init.d/network doesn't recognize the "probe" parameter (I have initscripts-6.91-3mdk) ! So linuxconf writes in its logfile: Execution de :/etc/rc3.d/S10network Utilisation : /etc/rc3.d/S10network {start|stop|restart|reload|status} * sh: line 1: stop: command not found * sh: line 1: restart: command not found * sh: line 1: reload: command not found * sh: line 1: status}: command not found * retourne 127 So, as solution, should /etc/init.d/network implement a "probe" option, or should linuxconf call to "/etc/rc3.d/S10network restart" ?