Issues with the terminal. /bin/ls works /usr/sbin/ls not

Question

I was having some weird issues today after my apache broke down completely. I had to reinstall apache and did so using apt-get install apache2.

Now, whenever I type ls it prints me: Compiled in modules: core.c mod_log_config.c mod_logio.c prefork.c http_core.c mod_so.c

The actual command does not work. Where as /bin/ls -la works. I think that looks like the other ls script is damaged.

All help is greatly appreciated.

Thanks!

could you perhaps clarify your question... when you run ls instead of getting a directory listing, you get a list of apache's compiled in modules? that doesn't make much sense.
You mention /usr/sbin/ls in the title, but not in the question. What's your evidence for thinking that /usr/sbin/ls is what's run when you run ls at the shell prompt?
@cpbills: I get: (98)Address already in use: make_sock: could not bind to address [::]:80 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs
@JdeBP: The /usr/sbin/ls command has a different output than the /bin/ls command. It seems the sbin ls has been malformed. I tested all Terminals in $PATH. All others work except /usr/sbin.
What on Earth does "all Terminals in $PATH" mean? If that's an answer to my question it's not a clear one. Again, what makes you think that /usr/sbin/ls is actually the program that you are running when you type ls at the command line? Indeed, what makes you think that /usr/sbin/ls is a script? What did you do to ask the shell what it runs for the ls command? What did you do to determine what the file /usr/sbin/ls contains?

Aaron · Answer 1 · 2011-08-19 11:39:51Z

up vote 0 down vote

Try reinstalling everything to solve it, that may help.

community wiki

feedback

1 Answer