The dot is short for the "source" command, I think. So if rc.pommed exits with something else than 0 rc.local quits and doesn't even try to run the remaining script.
I've learned this recently, so maybe someone more experienced can correct me if I'm wrong.
Try to disable pommed, if you chmod the rc-file like stated in the comment in your rc.local this should suffice hence the if-statement.

As MisterL stated, sourcing rc.pommed might be causing issues. Generally, you don't source rc. files, you want to execute them. I would remove the period in front of it as it is not common practice.

Next, I believe your su line is incorrect (not at a Linux box to check right now). If you want to run mpd as user "flint", I believe you need to specify the -c option with the command you want to run followed in quotes.

If you wanted to use the rc.mpd file, we'd need to see the contents of the file.

Thank you bassmadrigal, a thousand times over. My su command was ars about I should know not to blind cut and paste by now.

That did it. In rc.local. I see that my su command in rc.mpd was also back-to-front. However, after correcting rc.mpd, it still would not start automatically. Not to worry, I don't need one anyway



Dunno how that period got there MisterL, but pommed still starts anyway.In fact, rc.pommed wouldn't start untill I called it from rc.local. I have gotten rid of the period though and it still works

It's in my first post, but I have done away with it entirely now. One line in rc.local does the trick. Thanks again.

I still have to wait 30 seconds or so for client(ncmpcpp) to connect to mpd, but mpd now starts automaticaly on boot. I am happy. Thank you all for sharring.