Kel Modderman wrote:
# warning: # warning: stop script call of invoke-rc.d # warning: this is not supported by insserv # warning:
> I am not aware of any message generated by the insserv program which is
similar to it.
I made a photo of the shutdown messages scrolling away: --- Listening on LPT/eth1/.... Sending on LPT/eth1/.... Sending on Socket/fallback DHCPRELEASE on eth1 on .... send_packet: Network is unreachable send_packet: Please consult README file regarding broadcast ... invoke-rc.d: ---------------------------------------- invoke-rc.d: Warning: invoke-rc.d called during shutdown .... invoke-rc.d: initscript policy layer fallback to safe mode invoke-rc.d: ---------------------------------------- Reloading /etc/samba/smb.conf: smbd onlyNo process is pid.... bd.pid found running: none killed . Done. Cleaning up ifupdown.... Deactivating swap --- In the startscripts I found invoce-rc.d only in cups, which is not called during shutdown and in dbus where this function is called with a stop parameter: --- dependent_services() .... services=$(grep -s -l "^# Required-Start:.*dbus" /etc/rc${r}.d/S??* .... invoke-rc.d $service $action || true --- I tested by commenting out this invoke-rc.d for a shutdown: /etc/init.d it is NOT the cause of my scary shutdown messages! (By the way I find this /etc/init.d/dbus script ugly: It does on every start/shutdown what insserv alone should do for dependency sake) As an experimental affine sidux user I installed insserv half a year earlier than this package reached debian unstable. Now I guess there was a bad insserv installation long time ago. Why does my network and samba want to start when shuting down? What can I do to fix my system ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org