Kel Modderman wrote: > The non-executable script gets ignored, then later when insserv updates the > symlink farm based on the overall dependency graph (which doesn't include the > skipped script), symlinks to scripts which do not exist or are invalid are > removed.
Ok, so that is what the message wants to say. How about: insserv: script vsftpd is not executable, will be skipped in boot sequence! insserv: script vsftpd is not a regular file, will be skipped in boot sequence! The first message for non-executables, the second for directories and their kin. > (what about the other questions? :)) I'm totally fine with the service not being stopped at shutdown when the initscript is marked nonexecutable. I assume the crazy user is managing the service some other way. A good message would help her realize that the links have been touched and she needs to kick insserv again when reenabling the init script. If you actually wanted the answers: I don't have that setup any more, so I'm not any better placed to get the answers than more interested people. :) Thanks again, Jonathan _______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
