Date: Tue, 15 Jul 2003 08:59:03 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Kent Stewart <kstewart@owt.com> Cc: stacey@vickiandstacey.com Subject: Re: make index strangeness after today's cvsup of ports tree Message-ID: <20030715075903.GA67317@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <200307141851.51436.kstewart@owt.com> References: <1058214037.64468.42.camel@localhost> <20030714203606.GA52774@happy-idiot-talk.infracaninophile.co.uk> <1058216384.64468.45.camel@localhost> <200307141851.51436.kstewart@owt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--PNTmBPCT7hxwcZjr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Jul 14, 2003 at 06:51:51PM -0700, Kent Stewart wrote:
> On Monday 14 July 2003 01:59 pm, Stacey Roberts wrote:
> > On Mon, 2003-07-14 at 21:36, Matthew Seaman wrote:
> > > happy-idiot-talk:...ports/x11/xstroke:% make -V PORTSDIR
> > > cd: can't cd to /devel/libgnugetopt
> > > cd: can't cd to /devel/libgnugetopt
> > > cd: can't cd to /devel/libgnugetopt
> > > cd: can't cd to /devel/libgnugetopt
> > > cd: can't cd to /devel/libgnugetopt
> > > cd: can't cd to /devel/libgnugetopt
> > > cd: can't cd to /devel/libgnugetopt
> > > cd: can't cd to /devel/libgnugetopt
> > > cd: can't cd to /devel/libgnugetopt
> > > cd: can't cd to /devel/libgnugetopt
> > > cd: can't cd to /devel/libgnugetopt
> > > cd: can't cd to /devel/libgnugetopt
> > > cd: can't cd to /devel/libgnugetopt
> > > cd: can't cd to /devel/libgnugetopt
> > > ...
> > Thanks for that explanation.., I imagine this is another one of those
> > things that eventually sorts itself out..,
> The other thing that is happening is the following.from a dmesg
>=20
> maxproc limit exceeded by uid 0, please see tuning(7) and login.conf(5).
> maxproc limit exceeded by uid 0, please see tuning(7) and login.conf(5).
> maxproc limit exceeded by uid 0, please see tuning(7) and login.conf(5).
>=20
> You get 3 or 4 of these while all of the above is going on.
Yes. make(1) is invoking itself recursively because of this bug. The
aposite term is "fork bomb". Eventually you'll run out of system
resources and the command will fail. When Stacey said "sorts itself
out", I believe he was talking about getting fixes committed to the
ports tree. He didn't mean that there would be loads of error
messages printed out, and then the command would succeed anyhow.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--PNTmBPCT7hxwcZjr
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)
iD8DBQE/E7RHdtESqEQa7a0RAhTcAJ9d3DHTpUtLorpzigyooZJVAkbRNACggVve
/R4TcBFjYG2lnZ1pJ23s158=
=Cvij
-----END PGP SIGNATURE-----
--PNTmBPCT7hxwcZjr--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030715075903.GA67317>