tis 2014-01-28 klockan 12:15 -0700 skrev Alex Rousskov:
> but squid.conf location is already configurable via the command line.
> Why another option, that is now propagated to non-Windows builds,
> without even defining what "service" is in non-Windows context (AFAIK).
If I am not mistaken the se
On 01/28/2014 11:56 AM, Henrik Nordström wrote:
> tis 2014-01-28 klockan 11:25 -0700 skrev Alex Rousskov:
>
>> Why do we need a command line option to specify a service name? Can the
>> service name be configured via squid.conf? The squid.conf location is
>> already configurable via command line,
tis 2014-01-28 klockan 11:25 -0700 skrev Alex Rousskov:
> Why do we need a command line option to specify a service name? Can the
> service name be configured via squid.conf? The squid.conf location is
> already configurable via command line, of course.
If I remember correctly the service name is
On 11/01/2013 07:11 AM, Amos Jeffries wrote:
> -n - Windows service name
>
> The Windows build of Squid requires a -n option to point at the
> particular named service which is running in the background. Which
> defaults to the name "squid" when omitted.
Why do we need a command line option to s
