Package: squid Version: 4.6-1 Severity: normal Tags: patch Hi,
first of all: I'm running sysvinit-core instead of systemd. When squid starts and the cache directory structure below /var/spool/squid doesn't exist yet, /etc/init.d/squid calls `squid -z -f $CONFIG` to create the directories and start-stop-daemon thereafter for the actual launch. `squid -z` however seems to fork to the background, making start-stop-daemon think it's already running (return code 1). Adding -N to `squid -z` (No daemon mode) solved the issue for me: `squid -z` only returns after the directory structure has been created, letting start-stop-daemon do its job. Cheers Daniel -- System Information: Debian Release: 10.0 APT prefers proposed-updates Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Shell: /bin/sh linked to /usr/bin/bash Init: sysvinit (via /sbin/init)
