ports/63264: ports www/squid & www/squid24 change startup behaviour depending on installed ports
Oliver Eikemeier
eikemeier at fillmore-labs.com
Mon Feb 23 13:10:07 UTC 2004
>Number: 63264
>Category: ports
>Synopsis: ports www/squid & www/squid24 change startup behaviour depending on installed ports
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Feb 23 05:10:06 PST 2004
>Closed-Date:
>Last-Modified:
>Originator: Oliver Eikemeier
>Release: FreeBSD 4.9-STABLE i386
>Organization:
Fillmore Labs - http://www.fillmore-labs.com
>Environment:
System: FreeBSD nuuk.fillmore-labs.com 4.9-STABLE
>Description:
PR 61315 and PR 62443 introduced
unset rcNG
if [ -f /etc/rc.subr ]; then
. /etc/rc.subr && rcNG=yes
else
if [ -f %%PREFIX%%/etc/rc.subr ]; then
. %%PREFIX%%/etc/rc.subr && rcNG=yes
fi
if [ "${rcNG}" ]; then
rcvar=`set_rcvar`
load_rc_config ${name}
run_rc_command "$1"
else
case $1 in
start)
[...]
in ${PREFIX}/etc/rc.d/squid.sh. On a 4.x machine Both ports start unconditionally when
rc.subr is not installed, and depending on squid_enable="YES" in /etc/rc.conf when
sysutils/rc_subr is installed.
If I later install a port using sysutils/rc_subr, squid is no longer started at boot time,
which is quite unexpected. On the other hand if I deinstall sysutils/rc_subr, squid stops
obeying squid_flags from /etc/rc.conf
Btw, %%PREFIX%%/etc/rc.subr is not PREFIX-safe.
While I'm at it: the port CONFLICTS with itself.
>How-To-Repeat:
>Fix:
Just use USE_RC_SUBR=yes and source %%RC_SUBR%% as everybody else does.
Use CONFLICTS=squid-2.[0-34-9] and CONFLICTS=squid-2.[0-56-9].
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list