From owner-freebsd-bugs@FreeBSD.ORG Mon Dec 26 08:00:32 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F9241065670 for ; Mon, 26 Dec 2011 08:00:32 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 965008FC15 for ; Mon, 26 Dec 2011 08:00:31 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBQ80U5M043090 for ; Mon, 26 Dec 2011 08:00:30 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBQ80UDD043078; Mon, 26 Dec 2011 08:00:30 GMT (envelope-from gnats) Date: Mon, 26 Dec 2011 08:00:30 GMT Message-Id: <201112260800.pBQ80UDD043078@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: KES Cc: Subject: Re: misc/163038: can not connect through ssh to server when /usr is 100% busy X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: KES List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Dec 2011 08:00:32 -0000 The following reply was made to PR misc/163038; it has been noted by GNATS. From: KES To: bug-followup@freebsd.org,kes-kes@yandex.ru Cc: Subject: Re: misc/163038: can not connect through ssh to server when /usr is 100% busy Date: Mon, 26 Dec 2011 10:00:00 +0200 I am agree that you lock write operations, but why do you lock read operations too?