Hi whenever I shut down, I get maybe 50 or more messages saying something along the lines of

It doesn't appear to affect functionality - but it is very annoying. What is it that this is saying and why is it complaining about a line that doesn't even exist?

I've printed the output of k99local below. (It really just points to /etc/init.d/local - which contains some startup commands).


Any clue about what is going on and how to fix it?

GJ

i will take a guess
first
i think you shouldn't be calling this script at shutdown at all
it essentially initializes stuff for startup (late into startup) as you said
reading in some splash configs and then tweeking some kernel settings
the script is not divided up into K(kill) and S(start) parts like most startup script are
you could set it up that way but no reason -- there doesn't seem to be a reason to touch these issues at shutdown
so i would remove K(kill) runlevel references (links) to /etc/init.d/local

that of course wil fix the shutdown problem but you still have a syntax problem i think
(i'm not so good with bash scripting)
this line:
--device=/dev/input/event0"

you have a closing (") there that has no coresponding opening (")

most lkely EOF errors are bash searching for the lost (")

i also can't quite understand what that line is trying to do -- looks like a long argument to some script or program that has gotten lost from its home and is now causing troubles and possibly messing up those writes to /proc/mtrr

Mmm I tried commenting those splash lines out but I still get those errors during boot (and shutdown too).

Actually I'm getting a few unknown commands during startup/shutdown such as

"sbin/unconfigured.sh No such file or directory"

"grep /proc/cmdline No such file or directory"

and also

"warning process "update" used the obsolete bdflush sytem call."

I'm not sure if they are all related, but I am on a bit of a quest to eliminate as many bugs (minor or otherwise) as I can.

I don't think I've ever had a linux system that stated up and shutdown 100% cleanly without complaints, it would be nice for once to see it.

Is there any chance anyone here knows which script in debian is issuing these commands? It's not the local script, as this is I assume soomething that I am expected to add my own commands to - so it must be some other general start up script that controls the behavour of the whole system and that even overrides all the settings in /etc/init.d/local.

I am also still getting the unexpected EOF issues - and the referrence to the non existant 'line 15" in /etc/init.d/local and also the system is continuing to attempt to load several modules at boot time, despite having compiled them (as they weren't needed) out of my kernel and having run update-modules. So why the sytem isn't listening to me is something of a concern.

I am simply somewhat nervous that some of these errors might be telling me that something much more fundamental is wrong - which is why I would like to pin down what it is that is causing them.

Any input anyone can offer will be extremely welcome.

GJ