Date: Fri, 18 Jul 2014 07:34:22 -0700 (PDT) From: Beeblebrox <zaphod@berentweb.com> To: freebsd-ports@freebsd.org Subject: Re: When poudriere jails become stuck in a loop Message-ID: <20140718173407.4ae403dc@rsbsd.rsb> In-Reply-To: <1405692361821-5929843.post@n5.nabble.com> References: <1405676493174-5929736.post@n5.nabble.com> <53C92530.10008@astart.com> <1405692361821-5929843.post@n5.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It just occurred to me that I should mention I use core unlocking. My CPU: AMD-AthlonII-X3-460, with 4th core unlocked making it an X4-460. On the other hand, I have seen two poudriere jails stuck in loops at the same time (out of running 4), which may not mean much since instructions from jail are picked up by any available core. Something else I have noticed lately is that my 4G swap keeps running out of space: "swap_pager_getswapspace(4): failed". This is probably a result of the stuck jail and not a cause IMHO. ----- FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/When-poudriere-jails-become-stuck-in-a-loop-tp5929736p5929861.html Sent from the freebsd-ports mailing list archive at Nabble.com. From owner-freebsd-ports@FreeBSD.ORG Fri Jul 18 14:51:46 2014 Return-Path: <owner-freebsd-ports@FreeBSD.ORG> Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8580E22C; Fri, 18 Jul 2014 14:51:46 +0000 (UTC) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) by mx1.freebsd.org (Postfix) with ESMTP id 564B42C95; Fri, 18 Jul 2014 14:51:46 +0000 (UTC) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id D60F75A9F0B; Fri, 18 Jul 2014 14:51:38 +0000 (UTC) Date: Fri, 18 Jul 2014 14:51:38 +0000 From: Brooks Davis <brooks@freebsd.org> To: Baptiste Daroussin <bapt@freebsd.org> Subject: Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg? Message-ID: <20140718145138.GB11456@spindle.one-eyed-alien.net> References: <CAG=rPVcyqq2072+gF_X91BocxykJB6+U0cMhaNexxfVFpVqUbA@mail.gmail.com> <CAJ-Vmo=p6-7KCL8C09O4dPq04pitW5wDbtsDAyz-u4Qtr7rpRA@mail.gmail.com> <CAGZBXN8-Gq1=w8SBHCw26ZX4a29KHBx+4FV9XGK1HJiCOGuJ9A@mail.gmail.com> <CAJ-Vmo=8uAXqmX8D+oP+63dHWVKN6cn8wBH0HNsVmUciNRF1BA@mail.gmail.com> <53C82EC4.8060304@gmail.com> <CAPS9+SuswkJNuwhT=o+7sBQpbaN0-jhnRK5drugqZw54+qzgzA@mail.gmail.com> <20140717205445.GC28314@ivaldir.etoilebsd.net> <CAJ-VmomejC3K7hy1DnwXncbY_H13U17gEpezhK5v+_KHNPHR=A@mail.gmail.com> <20140717210738.GE28314@ivaldir.etoilebsd.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RASg3xLB4tUQ4RcS" Content-Disposition: inline In-Reply-To: <20140717210738.GE28314@ivaldir.etoilebsd.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Craig Rodrigues <rodrigc@freebsd.org>, Adrian Chadd <adrian@freebsd.org>, Navdeep Parhar <nparhar@gmail.com>, freebsd-doc@freebsd.org, Alberto Mijares <amijaresp@gmail.com>, freebsd-current Current <freebsd-current@freebsd.org>, Andreas Nilsson <andrnils@gmail.com>, ports <freebsd-ports@freebsd.org> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>; List-Post: <mailto:freebsd-ports@freebsd.org> List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 18 Jul 2014 14:51:46 -0000 --RASg3xLB4tUQ4RcS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 17, 2014 at 11:07:39PM +0200, Baptiste Daroussin wrote: > On Thu, Jul 17, 2014 at 01:57:52PM -0700, Adrian Chadd wrote: > > On 17 July 2014 13:54, Baptiste Daroussin <bapt@freebsd.org> wrote: > > > On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote: > > >> On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar <nparhar@gmail.com>= wrote: > > >> > > >> > On 07/17/14 13:12, Adrian Chadd wrote: > > >> > > On 17 July 2014 13:03, Alberto Mijares <amijaresp@gmail.com> wro= te: > > >> > >> On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd <adrian@freebsd.o= rg> > > >> > wrote: > > >> > >>> Hi! > > >> > >>> > > >> > >>> 3) The binary packages need to work out of the box > > >> > >>> 4) .. which means, when you do things like pkg install apache,= it > > >> > >>> can't just be installed and not be enabled, because that's a b= it of a > > >> > >>> problem; > > >> > >> > > >> > >> > > >> > >> No. Please NEVER do that! The user must be able to edit the fil= es and > > >> > >> start the service by himself. > > >> > > > > >> > > Cool, so what's the single line command needed to type in to sta= rt a > > >> > > given package service? > > >> > > > >> > Aren't sysrc(8) and service(8) for this kind of stuff? > > >> > > > >> > > >> They sure are. > > >> > > >> Well, pkg install $service ; sysrc ${service}_enable=3D"YES" would d= o. > > >> Although some services have different names than the packge, which i= s sort > > >> of annoying. > > > > > > Maybe service needs to be extended (seriously sysrc ${service}_enable= =3D"YES" is > > > not user friendly) we have service -l that list the services, maybe a= service > > > ${service} on that create /etc/rc.conf.d/${service} with ${service}_e= nable=3D"YES" > > > in it and service ${service} off to remove it > > > > > > maybe service -l could also be extended to show the current status (m= aybe with a > > > -v switch) > > > > > > but for sure having the service off by default is a good idea :) > >=20 > > Yeah, maybe having it populate an entry of service_enable=3D"NO" for no= w . >=20 > then you need to extend rcng to support /usr/local/etc/rc.conf.d so the p= ackages > can install them without touching base :) and we will need to wait for all > supported FreeBSD version to have the said modification) Here's a totally untested patch to do that. I was rather surprised that this wasn't configurable already. -- Brooks Index: defaults/rc.conf =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- defaults/rc.conf (revision 268825) +++ defaults/rc.conf (working copy) @@ -56,6 +56,7 @@ local_startup=3D"/usr/local/etc/rc.d" # startup script dirs. script_name_sep=3D" " # Change if your startup scripts' names contain spac= es rc_conf_files=3D"/etc/rc.conf /etc/rc.conf.local" +rc_conf_dirs=3D"/etc/rc.conf.d /usr/local/etc/rc.conf.d" =20 # ZFS support zfs_enable=3D"NO" # Set to YES to automatically mount ZFS file systems Index: rc.subr =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- rc.subr (revision 268825) +++ rc.subr (working copy) @@ -1289,10 +1289,12 @@ fi _rc_conf_loaded=3Dtrue fi - if [ -f /etc/rc.conf.d/"$_name" ]; then - debug "Sourcing /etc/rc.conf.d/${_name}" - . /etc/rc.conf.d/"$_name" - fi + for _dir in ${rc_conf_dirs}; do + if [ -f "$_dir"/"$_name" ]; then + debug "Sourcing ${_dir}/${_name}" + . "$dir"/"$_name" + fi + done =20 # Set defaults if defined. for _var in $rcvar; do --RASg3xLB4tUQ4RcS Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlPJNHoACgkQXY6L6fI4GtQtAgCgzH7lveN/16Obli4FeZgtOW4N ga4AoKw1zKsRvDeS7rvpO6aSfYajH7vZ =6S6v -----END PGP SIGNATURE----- --RASg3xLB4tUQ4RcS--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140718173407.4ae403dc>