Date: Sun, 19 Dec 2004 21:52:39 +0100 From: Erik Norgaard <norgaard@locolomo.org> To: cpghost@cordula.ws Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Getting back my shell is slow, Eterm/bash Message-ID: <41C5EA17.5040300@locolomo.org> In-Reply-To: <20041219192729.GA1668@bsdbox.farid-hajji.net> References: <41C5A5A1.5000401@locolomo.org> <20041219192729.GA1668@bsdbox.farid-hajji.net>
next in thread | previous in thread | raw e-mail | index | archive | help
cpghost@cordula.ws wrote: > I've noticed this too, but not only with the console. Just wild > guessing: the scheduler needs a long time to wake up processes > that have been swapped out. I don't know if this bug has been (completely) > fixed yet, 'cause I have no machine that I could upgrade right now. > > Just check if the sleepy shell has been swapped out before. This bug has > been often reported in disguise (X takes long time to exit, ssh takes > long time to connect, whatever). It's often not the exiting process' > fault, but the swapped out parent's or daemon's long wakeup latency. > > But again, I'm just wildguessing. This bug may well have been fixed > since last time I've cvsup-ed. Thanks, at least I have a good explanation that doesn't suggest I am just overlooking the obvious :-) I have only noticed it under X, and only with the shell, and only when terminating some program started from the console. But, I'll be patient and try another update :-) Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41C5EA17.5040300>