Date: Wed, 17 Jun 2009 10:13:52 -0400 From: Robert Huff <roberthuff@rcn.com> To: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: portupgrade/ruby issue? (Stale lock file was found. Removed.) Message-ID: <19000.64032.525753.249900@jerusalem.litteratus.org> In-Reply-To: <44tz2f9gpb.fsf@lowell-desk.lan> References: <4A38B47E.1070906@icyb.net.ua> <20090617133231.3883776a@sub.han.vpn.gamesnet.de> <19000.55863.785195.669767@jerusalem.litteratus.org> <44tz2f9gpb.fsf@lowell-desk.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Lowell Gilbert writes: > >> > After recent massive ports update (I think ruby was touch and > >> > probably portupgrade too) I started getting seemingly sporadic "Stale > >> > lock file was found. Removed." messages. What's interesting is that > >> > those messages are produced on stdout, not stderr. > >> > >> Got the same on five 7-Stable Machines. > > > > And on -Current from April. So, not a function of the OS version. > > Mine happens every time I run portupgrade/portversion, even > > when prior runs completed successfully. > > It seems harmless, but it would be Really Nice if it were > > fixed. > > Not *completely* harmless; running separate portupgrade processes > in parallel is pretty risky at the moment... When was it officually cleared to do that? Last I knew it was "do at your own risk". Robert Huff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19000.64032.525753.249900>