Re: catnip.local (redirect)
Hmm. All this made me look at how I have this box set up and I discover that what I was about to tell you (and what I've done to a box I'm borrowing from work) was wrong. I'lll try to reconstruct things. I hope I make sense. My spouse has, at her workplace, a Mac OS X machine with web sharing turned on. This machine is, therefore, reachable on the internal company LAN as either http://catnip.local or http://catnip.company.com If my memory is right, I used to get that back in the days of 10.0 when the link went down or the ethernet cable came slightly loose or whatnot. /etc/hosts was only referenced during single user mode back then or something. I can't remember if using the machines "domain" in netinfo was the cause or the cure. But if you look under /machines in the Applications/Utilities/netinfo GUI widget, you'll notice that there are two entries that look very suspicious. At one time I had added an entry under /machines for the name of this box. I duplicated the localhost entry and edited it in a way that seemed appropriate. Sometime between 10.0 and 10.2.8, Apple fully restored the functionality of /etc/hosts, so I presently have a line something like 10.2.40.49 reiisi reiisi.homedns.org in /etc/hosts, instead. When she works from home, she accesses the company network via VPN. The machine is still accessible as http://catnip.company.com. Unfortunately, many of the links automatically convert too URLs beginning catnip.local. Via VPN (the way she does it), there is no catnip.local. I was going to mumble something here, but I need to hit the hay. I'm not sure I'm making any sense anymore anyway. Does anyone know where this redirection to catnip.local is stored and whether (how) she can make it stop? -r -- email: [EMAIL PROTECTED]; phone: +1 650-873-7841 http://www.cfcl.com- Canta Forda Computer Laboratory http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc. http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series
Re: catnip.local (redirect)
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
[OT] Re: catnip.local (redirect)
My spouse has, at her workplace, a Mac OS X machine with web sharing turned on. This machine is, therefore, reachable on the internal company LAN as either http://catnip.local or http://catnip.company.com [] other places to look at for grins and giggles -- man hostname man domainname cat /etc/hostconfig (/etc/hostconfig is what actually tells the box to name itself automatically, which is causing the use of the local domain, but don't jump to the assumption that you should therefore change it from automatic to catnip.company.com. I don't remember why I don't do that, but I did think I had a good reason. Looking up "etc/hostconfig"+"mac os x" at your favorite search engine might provide some clues.) The biggest failing with mac os x is its biggest strength -- too much indirection and delegation. It's often really difficult to figure out where the buck stops. But it does "just work" for most people, and they do seem to be making headway at sorting things out so that mere mortal sysads can figure them out. Have you asked/searched on Apple's boards and mailing lists? I'm pretty the topic has floated there in the past. -- Joel Rees Nothing to say today so I'll say nothing: Nothing.
