From owner-freebsd-current@FreeBSD.ORG Mon Jul 12 04:05:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7232D16A4CE for ; Mon, 12 Jul 2004 04:05:43 +0000 (GMT) Received: from mail011.syd.optusnet.com.au (mail011.syd.optusnet.com.au [211.29.132.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5383343D2D for ; Mon, 12 Jul 2004 04:05:42 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) i6C45W602271; Mon, 12 Jul 2004 14:05:32 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i6C45VVd090912; Mon, 12 Jul 2004 14:05:32 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)i6C45U0d090911; Mon, 12 Jul 2004 14:05:30 +1000 (EST) (envelope-from pjeremy) Date: Mon, 12 Jul 2004 14:05:30 +1000 From: Peter Jeremy To: Markie Message-ID: <20040712040530.GA89608@cirb503493.alcatel.com.au> References: <000b01c46617$1f3ba4e0$f800000a@laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000b01c46617$1f3ba4e0$f800000a@laptop> User-Agent: Mutt/1.4.2i cc: freebsd-current@freebsd.org Subject: Re: quick interactivity? question regarding -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jul 2004 04:05:43 -0000 On Sat, 2004-Jul-10 01:44:51 +0100, Markie wrote: >In the mean time, I just wanted to ask a really quick question. Before 'the >update', and also back when it was running 4.x if I remember correctly, if >I left an ssh session logged in overnight on my computer when I woke up and >started to type it would take a while for what I typed to appear on my >console - as if the box had to wake up from suspend or something. If the systems are not blindingly fast and don't have massive amounts of RAM, the most likely cause of this is the idle ssh, sshd and shell being paged out by scheduled jobs. The delay is them being paged back in. > However, >now it's running -CURRENT I no longer seem to get this delay (which is >really good!). Are you doing something different as far as scheduled jobs are concerned? (Eg you've stopped running "make buildworld" overnight) The scope of changes in -current is probably enough to explain the different behaviour in any case. -- Peter Jeremy