From owner-freebsd-questions@freebsd.org Thu Nov 9 01:43:07 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3556EE625C7 for ; Thu, 9 Nov 2017 01:43:07 +0000 (UTC) (envelope-from edgar@pettijohn-web.com) Received: from mail.pettijohn-web.com (pettijohn-web.com [108.61.222.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.pettijohn-web.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 05E4C70BB6 for ; Thu, 9 Nov 2017 01:43:06 +0000 (UTC) (envelope-from edgar@pettijohn-web.com) Received: from FreeBSD (50.59.65.174 [50.59.65.174]) by mail.pettijohn-web.com (OpenSMTPD) with ESMTPSA id d0a43a16 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 8 Nov 2017 19:42:58 -0600 (CST) Date: Wed, 8 Nov 2017 19:42:36 -0600 From: Edgar Pettijohn To: Ernie Luzar Cc: Ian Smith , freebsd-questions@freebsd.org Subject: Re: Need help with rc.d script Message-ID: <20171109013818.GA31584@FreeBSD> References: <20171108021900.W9710@sola.nimnet.asn.au> <20171108043726.N72828@sola.nimnet.asn.au> <5A01F758.1050706@gmail.com> <20171109005843.E72828@sola.nimnet.asn.au> <5A0332D1.90509@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5A0332D1.90509@gmail.com> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Nov 2017 01:43:07 -0000 On Wed, Nov 08, 2017 at 11:37:37AM -0500, Ernie Luzar wrote: > Ian Smith wrote: > > On Tue, 7 Nov 2017 13:11:36 -0500, Ernie Luzar wrote: > > > > > Thanks Ian, > > > Ending the while loop with "done &" worked. > > > > The one with or without the enclosing ( and ) to force a subshell? > > > > > When I issue dynip from the command line it runs as a daemon but I have to > > > use the kill command to stop it. > > > > > > This is my rc.d script for dynip script. issuing "service dynip start" works > > > but "service dynip stop" gives message saying > > > dynip not running? (Check /var/run/dynip.pid). Well ps ax shows it is running > > > and I have to use the kill command to stop it. > > > > Things to check: > > > > . after 'start' does /var/run/dynip.pid exist while it's running?? > > . if so, does it contain the same PID as 'ps ax' shows for dynip? > > . does 'ps ax' show a different PID for the subshell, if there is one? > > . Does /var/run/dynip.pid still exist after running 'stop'? > > > > i.e. is the PID needed for kill the same as that in /var/run/dynip.pid? > > > > > Here is my rc.d script. What am I missing to populate the dynip.pid file so > > > "service dynip stop" command will work? > > > > > > #!/bin/sh > > > # > > > # > > > # PROVIDE: dynip > > > # REQUIRE: LOGIN > > > # KEYWORD: nojail shutdown > > > # > > > # Add the following line to /etc/rc.conf to enable dynip: > > > # > > > # dynip_enable="YES" > > > # > > > > > > . /etc/rc.subr > > > name="dynip" > > > rcvar=dynip_enable > > > command="/usr/local/sbin/${name}" > > > pidfile="/var/run/${name}.pid" > > > load_rc_config ${name} > > > run_rc_command "$1" > > > > I've very little knowledge of the detailed behaviour of the rc system. > > Let's see how the above questions might inform before speculating .. > > > > cheers, Ian > > > > I tested with and without the enclosing ( and ) on the while loop and it > made no difference. No pidfile exists before the "service dynip start" > is issued and non exists afterwards. > I don't believe the rc system can write a pidfile for you. Most of if not all of the services being started by the rc system are written in c and take care of writing their own pidfile. I suspect you could overcome this by writing a c program that does so and executes your script every 10 minutes. Or some form of pgrep perhaps. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"