Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263738AbTFDRkI (ORCPT ); Wed, 4 Jun 2003 13:40:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263742AbTFDRkI (ORCPT ); Wed, 4 Jun 2003 13:40:08 -0400 Received: from windsormachine.com ([206.48.122.28]:15120 "EHLO router.windsormachine.com") by vger.kernel.org with ESMTP id S263738AbTFDRkH (ORCPT ); Wed, 4 Jun 2003 13:40:07 -0400 Date: Wed, 4 Jun 2003 13:53:36 -0400 (EDT) From: Mike Dresser To: Subject: RE: [PATCH] [2.5] Non-blocking write can block In-Reply-To: <019801c32abc$c233d1a0$ca41cb3f@amer.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 768 Lines: 18 On Wed, 4 Jun 2003, Hua Zhong wrote: > We ran into this problem here in an embedded environment. It causes > syslogd to hang and when this happens, everybody who talks to syslogd > hangs. Which means you may not even be able to login. In the end we used > exactly the same fix which seems to work. I get this problem with writing to a remote syslog server, if the remote syslog server hangs up or crashes no one can login to the machine that is writing to the syslog server, even when the syslog server comes back. Mike - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/