From owner-freebsd-ports@freebsd.org Wed Aug 30 14:11:03 2017 Return-Path: Delivered-To: freebsd-ports@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 318ACE02F52; Wed, 30 Aug 2017 14:11:03 +0000 (UTC) (envelope-from crees@physics.org) Received: from mail37c50.megamailservers.eu (mail161c50.megamailservers.eu [91.136.10.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 56D2D6E94F; Wed, 30 Aug 2017 14:11:01 +0000 (UTC) (envelope-from crees@physics.org) X-Authenticated-User: bayofrum.uwclub.net Received: from pegasus.bayofrum.net (host-80-41-56-156.as13285.net [80.41.56.156]) (authenticated bits=0) by mail37c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id v7UDr6Ai001600; Wed, 30 Aug 2017 13:53:08 +0000 Received: from [192.168.1.150] (zeus.bayofrum.net [192.168.1.150]) by pegasus.bayofrum.net (Postfix) with ESMTPSA id 7D080801DD; Wed, 30 Aug 2017 14:51:49 +0100 (BST) Subject: Re: pkg issue after FreeBSD 11 upgrade To: Cassiano Peixoto , Baptiste Daroussin Cc: freebsd-stable@freebsd.org, Matthew Seaman , "freebsd-ports@freebsd.org" References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> <20170830125950.mcp34sddcp6c757t@ivaldir.net> From: Chris Rees Message-ID: Date: Wed, 30 Aug 2017 14:51:49 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-bayofrum-MailScanner-Information: Please contact the ISP for more information X-bayofrum-MailScanner-ID: 7D080801DD.A05FC X-bayofrum-MailScanner: Found to be clean X-bayofrum-MailScanner-From: crees@physics.org X-Spam-Status: No X-CTCH-RefID: str=0001.0A0B0201.59A6C344.011E, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Rules: X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CSC: 0 X-CHA: v=2.2 cv=LIoWeNe9 c=1 sm=1 tr=0 a=eImF4KVNE/MQsd0gg/pNFQ==:117 a=eImF4KVNE/MQsd0gg/pNFQ==:17 a=IkcTkHD0fZMA:10 a=KeKAF7QvOSUA:10 a=6I5d2MoRAAAA:8 a=FWAKdnKL9gblLq5QA-kA:9 a=QEXdDO2ut3YA:10 a=IjZwj45LgO3ly-622nXo:22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2017 14:11:03 -0000 Cassiano Peixoto wrote: > Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal > with when I need to restart a service without upgrading? Reaper > functionnality is a trouble for many administrators who made meta ports to > manage their servers. I really think it could be a option to be > enabled/disabled. Can you see this possibility? > > Thanks. > > On Wed, Aug 30, 2017 at 9:59 AM, Baptiste Daroussin > wrote: > >> On Wed, Aug 30, 2017 at 09:55:22AM -0300, Cassiano Peixoto wrote: >>> Hi Baptiste, >>> >>> Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only. >> It only worked on FreeBSD 10 prior to 10.2, the reaper functionnality in >> freebsd >> kernel appeared in 10.2 >>> Cron is just an example, I manage more than 50 FreeBSD servers, and I've >>> been using ports for years to update some configs and restart the service >>> on all of them. Many times I need to change nginx config, ldap, etc. I >> just >>> need to restart the service. >> HANDLE_RC_SCRIPTS=true in your pkg.conf and pkg will automatically restart >> anything rc script provide once the package containing it is upgrading. >> >> This is off by default because in many cases it is dangerous (database >> upgrades, >> dovecot like things upgrade etc). But if you know what you are doing it >> does the >> job. >> >> Best regards, >> Bapt >> > Hey, I think you also want process supervision given your other comments. You can do this easily using daemon -P to run your scripts (but you'd need to rewrite the rc script...) Or use runit or similar? You could implement "runlevels" with that if that's REALLY what you want :) Cheers, Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.