From owner-freebsd-current@FreeBSD.ORG Wed Feb 15 17:59:20 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 04EF016A420 for ; Wed, 15 Feb 2006 17:59:20 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A85743D45 for ; Wed, 15 Feb 2006 17:59:19 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by zproxy.gmail.com with SMTP id o37so1662234nzf for ; Wed, 15 Feb 2006 09:59:18 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Pis6qmLpaydyj6U+ywpVrPq6pzsIYtEQVMXWghMvssS+0/z6SkQh8aMMe/3GQeHwjxrI4oKKVyJIHqY1mO5kVmNQodXcH8/esKvz+ryHVbX47A7IZcq5XfdTCkH6IwZOtcMFFfeJ5EL3iktb4VbkFovr1PHhDmpAe9WXEj5B8Yg= Received: by 10.65.126.17 with SMTP id d17mr2825073qbn; Wed, 15 Feb 2006 09:59:18 -0800 (PST) Received: by 10.65.112.19 with HTTP; Wed, 15 Feb 2006 09:59:18 -0800 (PST) Message-ID: Date: Thu, 16 Feb 2006 01:59:18 +0800 From: Jiawei Ye To: Poul-Henning Kamp In-Reply-To: <30864.1139781541@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060212225911.M598@free.home.local> <30864.1139781541@critter.freebsd.dk> Cc: freebsd-current@freebsd.org Subject: Re: calcru: runtime went backwards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 15 Feb 2006 17:59:20 -0000 I still get calcru messages from kernel built with sources 2 hours ago cvsupped via cvsup12. When the system is under load, sshd and inetd can get these messages and stop responding to any requests. As the machine is at a remote site, my original idea was to keep sshd and inetd/telnetd running, so that when sshd freezes, I can telnet into the machine and restart sshd (from a security point of view, this is a bad thing, I know). But to my surprise, after sshd froze, telnetd won't respond either. Connection was built successfully but no login prompt appeared. At this time, any CGI script that httpd invokes will not run. Could this possibly be some problem with the pts code instead of the accounting code? Jiawei Ye -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming