Date: Wed, 23 Sep 2009 09:14:47 GMT From: Gerrit Kühn <gerrit@pmp.uni-hannover.de> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/139078: cfengine3: startup scripts broken, update needed Message-ID: <200909230914.n8N9El7H031640@www.freebsd.org> Resent-Message-ID: <200909230920.n8N9K3vK003730@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 139078
>Category: ports
>Synopsis: cfengine3: startup scripts broken, update needed
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Sep 23 09:20:02 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: Gerrit Kühn
>Release: 7.2
>Organization:
AEI
>Environment:
7.2-stable amd64
>Description:
1. The startup scripts coming with the port do not work, because they use names like "name="cf-serverd"". This makes the following statements like
: ${cf-serverd_enable="NO"}
go wrong, because the shell treats the "-" as part of a variable substitution.
One possible solution is to go back to names like "cfserverd" (from cfengine2), but then conflicts may arise if cfengine2 is still installed. However, as this is not a recommended setup anyway, it would be probably a good idea to simply add cfengine2 as a conflicting port.
2. The port is still using cfengine3 version 3.0.1a7. Version 3.0.2 is out and recommended by the author as it fixes several bugs.
>How-To-Repeat:
Install cfengine3, put "cf-servered=YES" in /etc/rc.conf and try to run "/usr/local/etc/rc.d/cf-serverd start".
>Fix:
See above:
- change back names to cfserverd and cfexecd
- add conflicts line
- update to version 3.0.2
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200909230914.n8N9El7H031640>