Date: Sat, 7 Feb 1998 22:49:48 -0500 From: "Evan Champion" <evanc@synapse.net> To: <cvs-ports@FreeBSD.ORG> Subject: Re: cvs commit: ports/www/squid12 Makefile ports/www/squid12/patches patch-ak patch-al Message-ID: <02a501bd3444$9a5f4fc0$2844c00a@cello.synapse.net>
next in thread | raw e-mail | index | archive | help
> Evan sent me a port update moments after I committed one. Pick out some > of the changes he's made.. (Although I'm not so sure about moving the > cache to /var/spool/squid...) Maybe I'm just an old-fashioned kind of guy :-) but as I was saying to Peter, /usr/local/squid seems to be an _awful_ place to put squid's cache. I mean, /usr/local is a hideous enough creation without adding anything else to it :-) So, I thought about it for a bit, and putting the cache under /var/spool/squid was my best idea. Ideally, it would be something like logs under /var/log, pid under /var/run, and the cache would start directly under /var/spool/squid (instead of a /var/spool/squid/cache). Unfortunately, there isn't way to do that using configure. We could run the conf file through sed to fix it up a bit -- that would certainly be nice for the pid and logs. That still leaves the cache, and I think irrespective of what people think of the rest of the paths, the cache belongs under /var/spool/squid. Anyway, flames to me, not Peter. Evan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?02a501bd3444$9a5f4fc0$2844c00a>