Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: Squid config
- To: tlug@example.com
- Subject: Re: tlug: Squid config
- From: simon@example.com (Simon Cozens)
- Date: 15 Feb 2000 13:08:31 GMT
- Delivered-To: simon-outgoing@example.com
- Organization: Earth.li Origins
- References: <lists.tlug/20000215075601.A13866@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
- User-Agent: slrn/0.9.5.3 (UNIX)
(I'm back on the list. simon@example.com hasn't been receiving anything recently, so I subscribed as simon@example.com - if some admin-type has the time to look see where my mail's been going, I'd appreciate it.) Subba Rao (lists.tlug): >The cache_peer values have the following settings. > >cache_peer myhost.mydomain.com parent 3128 3130 [proxy-only] This is probably not what you want. You're saying that *all* the hosts on your network are running caches that you should peer with. While that might be the case, it's unlikely. I have *no* cache peers. If you're thinking about the ways to give access to your hosts, what you want is the http_access stuff lower down. You'll want something like this: acl myself srcdomain mydomain.com http_access allow myself -- "Even if you're on the right track, you'll get run over if you just sit there." -- Will Rogers -------------------------------------------------------------------- Next Nomikai Meeting: February 18 (Fri) 19:00 Tengu TokyoEkiMae Next Technical Meeting: March 11 (Sat) 13:00 Temple University Japan * Topic: TBD -------------------------------------------------------------------- more info: http://www.tlug.gr.jp Sponsor: Global Online Japan
- Follow-Ups:
- Re: tlug: Squid config
- From: Subba Rao <subb3@example.com>
Home | Main Index | Thread Index
- Prev by Date: tlug: Squid config
- Next by Date: Re: tlug: Squid config
- Prev by thread: tlug: Squid config
- Next by thread: Re: tlug: Squid config
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links