It seems this is caused by the empty "timeout" value in /etc/apt-proxy/apt-proxy-v2.conf.
If that line is commented out the daemon will start and appears to function normally (so far).
signature.asc
Description: Digital signature
It seems this is caused by the empty "timeout" value in /etc/apt-proxy/apt-proxy-v2.conf.
If that line is commented out the daemon will start and appears to function normally (so far).
signature.asc
Description: Digital signature