From owner-freebsd-rc@FreeBSD.ORG Mon Dec 17 18:30:42 2012 Return-Path: Delivered-To: freebsd-rc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DF99CAE6 for ; Mon, 17 Dec 2012 18:30:42 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 5BF618FC0A for ; Mon, 17 Dec 2012 18:30:41 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.5/8.14.5) with ESMTP id qBHIUfZH034719 for ; Mon, 17 Dec 2012 11:30:41 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id qBHIUdhv063083; Mon, 17 Dec 2012 11:30:39 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) Subject: Re: rc.subr questions - continued From: Ian Lepore To: Paul Schmehl In-Reply-To: <09612E06DF09112FB130CEC8@utd71538.campus.ad.utdallas.edu> References: <8A328288ADDF512269BB31D5@utd71538.campus.ad.utdallas.edu> <1355764632.1198.162.camel@revolution.hippie.lan> <09612E06DF09112FB130CEC8@utd71538.campus.ad.utdallas.edu> Content-Type: text/plain; charset="us-ascii" Date: Mon, 17 Dec 2012 11:30:38 -0700 Message-ID: <1355769038.1198.163.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-rc@freebsd.org X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2012 18:30:42 -0000 On Mon, 2012-12-17 at 11:43 -0600, Paul Schmehl wrote: > --On December 17, 2012 10:17:12 AM -0700 Ian Lepore > wrote: > > > On Mon, 2012-12-17 at 10:50 -0600, Paul Schmehl wrote: > >> Since I maintain three ports (security/sguil-server, > >> security/sguil-sensor and security/sguil-client) that have this > >> problem, I decided to start with the server port. The current port > >> version is 0.7.0 and the init script worked fine when I submitted the > >> port a while ago. Here it is: > > > > I can't answer the part about why it used to work and now it doesn't, > > but in general that doesn't look like a modern rc script that starts and > > stops a daemon. > > > > Someone had a similar problem with a simple solution in the past... > > > > http://lists.freebsd.org/pipermail/freebsd-questions/2010-October/222354. > > html > > > > Unfortunately, that doesn't work for me. Here's the current script: > > . /etc/rc.subr > > name="sguild" > load_rc_config ${name} > # set some defaults > sguild_enable=${sguild_enable:-"NO"} > sguild_conf=${sguild_conf:-"/usr/local/etc/sguild/sguild.conf"} > sguild_pid=${sguild_pid:-"/var/run/sguild/sguild.pid"} > sguild_flags=${sguild_flags:-"-D -P ${sguild_pid}"} > sguild_user=${sguild_user:-"sguil"} > > command="/usr/local/bin/${name}" > command_args="-c ${sguild_conf} ${sguild_flags}" > procname="/usr/local/bin/tclsh8.5" > start_cmd="sguild_start" > > sguild_start(){ > echo "starting sguild." > /bin/sh ${command} ${command_args} > } > > run_rc_command "$1" > > When I run start, I get this: > > # /usr/local/etc/rc.d/sguild start > starting sguild. > /usr/local/etc/rc.d/sguild: unknown directive '/usr/local/bin/sguild'. > Usage: /usr/local/etc/rc.d/sguild > [fast|force|one|quiet](start|stop|restart|rcvar|status|poll) > > Status and stop work fine. > > The "unknown directive is coming from line 913 in rc.subr: > echo 1>&2 "$0: unknown directive '$rc_arg'." > rc_usage $_keywords > # not reached > > rc_arg is (fast|force|one|quiet)(start|stop|restart|rcvar|status|poll). > > This error: > /usr/local/etc/rc.d/sguild: unknown directive '/usr/local/bin/sguild'. > > Seems to indicate that the rc.subr script thinks $0 is > /usr/local/bin/sguild rather than /usr/local/etc/rc.d/sguild, which is odd > to me. > > Does running with rc_debug=YES provide any extra clues? -- Ian