'Unable to open logs' points to a permission problem ... the only reason an app can't write to a log is if it was launched with lower permissions than the log directory requires.
It is possible (worth checking, anyway) that you need to run the apache server as root in order for it to have access to things like logs, sockets, etc..
Yeah, I figured it was something to that extent. Like I said, it worked when I typed sudo first.
And now I'm researching on windows/linux networking
Alrighty.... samba is all set up and I am able to access my files on my linux box from windows... BUT I can't write anything. I made sure that write permission was enabled in the share options, and I gave myself write permission in the samba config file.
At this point I'm 90% satisfied. I doubt I'll have to update the server files too much, so burning a cd with the files isn't too much hassle.
But one last question. Right now my apache root is pointed to a folder called "server_files". If I wanted to display a webpage rather than a directory listing, what settings should I change? I tried just sticking a file called index.htm into the folder, but it still came up with the directory listing.