Date: Wed, 17 Jun 2009 08:40:16 -0400 From: Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> To: Robert Huff <roberthuff@rcn.com> Cc: Tobias lott <tlott@gamesnet.de>, FreeBSD Ports <freebsd-ports@freebsd.org>, sem@freebsd.org Subject: Re: portupgrade/ruby issue? (Stale lock file was found. Removed.) Message-ID: <44tz2f9gpb.fsf@lowell-desk.lan> In-Reply-To: <19000.55863.785195.669767@jerusalem.litteratus.org> (Robert Huff's message of "Wed\, 17 Jun 2009 07\:57\:43 -0400") References: <4A38B47E.1070906@icyb.net.ua> <20090617133231.3883776a@sub.han.vpn.gamesnet.de> <19000.55863.785195.669767@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Huff <roberthuff@rcn.com> writes: > Tobias lott 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. >> > >> > Sporadic - because they appear when there are no parallel execution >> > of any portupgrade tools (or any other package/port related tools). >> > They appear in situations wheere they never appeared before. >> > >> > I see this on two stable/7 systems. >> >> 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...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44tz2f9gpb.fsf>