On Thu, 6 Jan 2005 18:52:00 -0500 (EST), Chris Devers <[EMAIL PROTECTED]> wrote:
> On Thu, 6 Jan 2005, Jeff Lowrey wrote:
> 
> > I might actually look at the apache configuration, and see if it's
> > using ServerName=catnip.local, and fix that.
> 
> This sounds like the right solution to me.
> 
> From what I can tell, if the ServerName directive is undefined in the
> Apache configuration, then it will default to the host name, which the
> Mac is going to see as `hostname`.local. If she manually specifies --
> 
>     ServerName catnip.company.com
> 
> -- in /etc/httpd/httpd.conf, then restarts Apache with a --
> 
>    $ sudo apachectl configtest && sudo apachectl restart
> 
> -- then everything should begin working properly.
> 
> Mucking around with the hosts file is the wrong way to fix this. For one
> thing, Panther doesn't even necessarily pay attention to it (by default
> it ignores it and most other files in /etc, if I remember right), but
> more importantly you're fixing the symptom (redirecting the host name)
> rather than the real problem (apache should use a portable name). Fix
> the real problem and the symptom will go away.
> 
> --
> Chris Devers
> 

Jaguar was braindamaged, but Panther exemines flat files before dns by
default, (I think it may not check ni /machines until after, though).

The important question, though, is which computer you want to
reconfigure, which computers you have administrator access to, and who
is going to do the work.  If your wife has administrator access to the
server at work (which may or may not be a vild assumption, depending
on what company she works for), then having her change the apache
configuration is certainly the "better" option all around, because it
then works for any computer that she connects through the VPN.

Modifying /etc/hosts, though, is a quick and easy solution for your
own computer at home, which doesn't risk offending her company's
system administrator if he/she is picky about who mucks around with
configuration files on corporate machines, and doesn't require messing
with the somewhat less-than-opaque apache configuration files and
directives.

HTH

--jay

Reply via email to