Apache doesn't start anymore
pixelized
stupid thing: after having edited it, i saved it on the desktop and
then i changed the file properties (permissions, owner and so on),
copying them from those ones belonging to the original file. Then i
replaced my new httpd.conf file with the original one, placed in httpd
folder. Now, if i try to turn on 'web sharing', from the sys prefs,
nothing happens (it says it is starting but it never starts). I see
that in the httpd folder there is a httpd.config.bak file, can i
enable it to somehow make it work?it is a copy of the httpd.conf
original file, isn't it? There's also a httpd.conf.default file, over
there... maybe it can be used too? you told to use sudo to edit
httpd.conf or bbedit shell, but isn't there any other way to edit (and
save!!) it? Thanks in advance, i hope you'll help me.
P.
PS: i'm running Panther 10.3.4 on a 1.25GHz PowerPCG4
David Phillip Oster
pixe...@nycmail.com (pixelized) wrote:
What did you use to edit it? A common mistake is to replace Unix line
separators (line-feed) with Macintosh line separators (carriage-return).
You can use The Finder's Get Info, to set the ownership and permissions.
(click on the "Details" disclosure triangle to get the U.I. you'll need.)
owner should be "root" (Shows as "system" in Finder), group should be
"wheel", read/write owner, read-only for group and all. Click on the
brass colored "lock" icon to unlock it for changes.
Disk Utilities' "Repair Permissions" might fix this for you.
Comparing httpd.conf and httpd.conf.bak shows that if you copy
httpd.conf.bak and rename it to httpd.conf it will probably work (you
might have to temporarily change the permissions on the directory
/etc/httpd/ to be able to work with files in it. Remember to set the
permissions on that directory back, when you are done.
pixelized
finder 'get info' window, but nothing happened and i've also used the
disk utility, as you said, to repair permissions, but the problem is
still the same. I'll try to rename and replace the .bak file, but i
guess that this won't work, i'll try, anymore. If you have any other
idea, i'll appreciate it! many thanks for your feedbacks!
P.
PS: I edited the conf file with simple text, just enabling some
feature, nothing more..
David Phillip Oster
> PS: I edited the conf file with simple text, just enabling some
> feature, nothing more..
I don't beleive that SimpleText properly handles Unix text file.
pixelized
thought it was fine to edit that...
must i edit the conf file from the shell (using sudo) and nothing
else? anyway: the problem i had is still alive... i know that i could
reinstall the whole sys, but i cannot stand it! i'd like to solve the
prob somehow, i think it would not be so difficult, but i have not
ideas..
many thanks anyway!
P.
David Phillip Oster
pixe...@nycmail.com (pixelized) wrote:
Well, I'm a programmer. Codewarrior has a popup menu on each window for
the line separator: Unix, Classic Mac, or MS-DOS. I'm familiar with it,
so that's what I use.
The free tool that Apple provides has a popup menu for the line
separator. (XCode in 10.3, formerly named Project Builder. An optional
install. If you don't already have a "Developer" folder in the top level
of your hard disk, look in Applications/Installers for the installer for
it.)
If that still doesn't let you fix the line separator, I'll e-mail you my
working conf file (in a disk image, so the e-mailer won't mess with it).
Just e-mail me asking for it.
Tom Harrington
I guess it could be related to line endings, as everyone else here seems
to think. But I'd be more inclined to guess that there's an error in
your edits, and that Apache can't start up because the config file
contains directives that it can't make sense of.
You can check on this by typing "apachectl configtest" at the command
line. It'll run through the various config files Apache finds, and tell
you about any errors it finds.
--
Tom "Tom" Harrington
Macaroni, Automated System Maintenance for Mac OS X.
Version 2.0: Delocalize, Repair Permissions, lots more.
See http://www.atomicbird.com/
Lester L.
I use Alpha when I need to edit files with Unix line endings on my Mac. I'm on
OS9, but the Mac OS X TeX/LaTeX Web Site mentions using Alpha, so it should work
for you.
http://www.kelehers.org/alpha/
And I echo the other poster's comment on using
apachectl
from the command line.
After your editing of conf files, etc, and need to restart, use
apachectl graceful
It will give you a line number with the errors in.
HTH
--
LesterOfPuppets
http://www.dangpow.com/~stumprok/
http://thedings.servebeer.com/