no i promise only litespeed was reading those files. Changing the config in litespeed admin for minmum perms fixed it. Actually if all systems were to read that config in litespeed they would read 000 files as well. I just happend to have a server read that config and was therefore reading 000 files. Changing that config to 0004 fixed it.
I doublechecked eveyrthing else, its not a server issue. Any other process or user will get access denied. I checked that first thing. It was just that server was reading that in litespeed admin. It is default 000. Not sure why this server was reading that config in litespeed but it did and the server was running with a minumum readable file as 000. Changing that number in litespeed admin to 0004 was the answer as I said above.
Last edited by felosi; 08-25-2008 at 11:17 AM..