Re: Stucking processes

Couldn't that just be because you're running a world that expects one
kernel but finds another? As far as I know, running a newer world in a jail
on an older system is not really recommended (while the opposite ought to
be ok)?
On Jun 16, 2012 11:33 AM, "Alexander Yerenkow" <yerenkow <at> gmail.com> wrote:

> Hello all.
> Since I'm using stable as host, and current in chroot, I'll write to
> both mail list, sorry for any inconvenience.
>
> My host is binary freebsd-updated 9;
> FreeBSD 9.0-RELEASE-p3 (GENERIC) #0: Tue Jun 12 02:52:29 UTC 2012
>
> I have chroot with latest current there installed r237089 (make
> buildworld && buildkernel, no specific flags)
> When I built from ports some programs in chroot all went fine, until I
> got stucked process automoc (when building kdelibs4);
> After few restarts I got build, and forget about it.
> I'm toying now with portupgrade, and see similar stucks in ruby18 and
> ruby19 (Even got few times in miniruby while building 1.8);
>
> Here's example of stucked processes (they aren't in top, and seems
> totally inactive. I haven't kill them yet, so can try to dig, but to
> where?):
>  2677   5  Is    0:00,00 | `-- /bin/sh
>  2678   5  I     0:00,00 |   `-- sudo su
>  2679   5  I     0:00,00 |     `-- su
>  2680   5  I     0:00,01 |       `-- _su (csh)
>  2687   5  I     0:00,03 |         `-- /bin/csh -i
>  2690   5  I+    0:04,34 |           `-- ruby19: portupgrade: [1/237]