[squid-users] Building squid | Best Practices?
hwaterfall at gmail.com
Sun Aug 30 17:42:03 UTC 2015
Thanks again, this is valuable information!
As you may have guessed, I'm asking about the user that should do builds to
ensure that the build outputs are created with the appropriate permissions
- I get a little concerned about security. It sounds like you are
suggesting that I simply create a directory for my custom builds:
I assign the --prefix option to the folder I create, so my build output
goes there, and then I make sure the permissions for that folder (and it's
sub-directories) are set for the user defined by *cache_effective_user* (and
the user defined by the ./configure option --*with-default-user*). Could
Finally (I hope), I've re-installed Ubuntu (various reasons, not just squid
issues) and I successfully installed squid using:
*sudo apt-get install squid3*
Squid wasn't found the first time:
*E: Unable to locate package squid3*
I had to run this first:
*sudo apt-get update*
However, when I try *apt-get build-dep squid,* I get:
*You must put some 'source' uris in your sources.list*
I can't seem to get over this problem. I've un-commented every line in
*/etc/apt/sources.list* that starts with deb-src.
Could you suggest a repository that I can add to */etc/apt/sources.list*?
On Sun, Aug 30, 2015 at 5:54 AM, Amos Jeffries <squid3 at treenet.co.nz> wrote:
> On 30/08/2015 1:07 p.m., Howard Waterfall wrote:
> > Great stuff thanks a lot! Excellent timing too just getting ready to do
> > make. I'll follow your suggestions. A couple of follow ups:
> > When doing the make (including ./configure), do I have to be running as
> > root or some particular user? I set up a squid user and user group and
> > a squidadm user group...
> You dont for the ./configure part.
> Make might need it to overwrite system files during the install part if
> you choose to replace the system files in-place. But that is just
> another reason to use a custom /proxy folder for the installation, which
> wont need root.
> > Finally I noticed that configure didn't have -x permissions with 3.5.7. I
> > guess I'll have to change that out of the gate...
> Hmm. Yes it should have -x permissions. Thanks for that I will have to
> double-check the 3.5.8 release.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the squid-users