Actually, I did not have a problem with the init script until _after_ I upgraded to 1:0.3.3-2. The install process stops with an error, and trying to start c-icap manually gives this error: "/etc/init.d/c-icap: 69: export: config_dsSocket /var/ru: bad variable name". The changelog indicates that init script hardening occurs in this version. I am unable to determine if the problem lies with my config file or if there is a bug in the init script. Replacing the new init script with the old one allows the install to finish and c-icap to start.

Here is my c-icap.conf file (with line numbers):

13:PidFile /var/run/c-icap/c-icap.pid
21:CommandsSocket /var/run/c-icap/c-icap.ctl
30:Timeout 300
39:MaxKeepAliveRequests 100
49:KeepAliveTimeout 600
58:StartServers 3
66:MaxServers 10
75:MinSpareThreads     10
84:MaxSpareThreads     20
92:ThreadsPerChild     10
103:MaxRequestsPerChild  0
111:Port 1344
122:User c-icap
133:Group c-icap
142:ServerAdmin xyz'at'domain.com
151:ServerName host.domain.com
159:TmpDir /tmp
169:MaxMemObject 131072
178:DebugLevel 1
186:ModulesDir /usr/lib/i386-linux-gnu/c_icap
194:ServicesDir /usr/lib/i386-linux-gnu/c_icap
204:TemplateDir/usr/share/c_icap/templates/
212:TemplateDefaultLanguage en
227:LoadMagicFile /etc/c-icap/c-icap.magic
238:RemoteProxyUsers off
247:RemoteProxyUserHeader X-Authenticated-User
255:RemoteProxyUserHeaderEncoded on
363:    acl localnet src 192.168.0.0/255.255.0.0
364:    acl localhost src 127.0.0.1/255.255.255.255
365:    acl all src 0.0.0.0/0.0.0.0
452:ServerLog /var/log/c-icap/server.log
467:AccessLog /var/log/c-icap/access.log
502:Service squidclamav squidclamav.so
546:Service echo srv_echo.so



Please advise and thanks.

Dale Schroeder

Reply via email to