Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755050AbZKFFRr (ORCPT ); Fri, 6 Nov 2009 00:17:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752598AbZKFFRr (ORCPT ); Fri, 6 Nov 2009 00:17:47 -0500 Received: from waste.org ([173.11.57.241]:37436 "EHLO waste.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751853AbZKFFRq (ORCPT ); Fri, 6 Nov 2009 00:17:46 -0500 Subject: Re: Using netconsole and getting double prints From: Matt Mackall To: "Luis R. Rodriguez" Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org In-Reply-To: <43e72e890911051654i19c18bf3nd397662ed79712c4@mail.gmail.com> References: <43e72e890911051654i19c18bf3nd397662ed79712c4@mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 05 Nov 2009 23:17:43 -0600 Message-ID: <1257484663.2873.622.camel@calx> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1043 Lines: 31 On Thu, 2009-11-05 at 16:54 -0800, Luis R. Rodriguez wrote: > I'm getting double prints when using netconsole. This used to happen > to me and then I just enable debugging log level manually (dmesg -n 8) > but now no matter what I try I always get double prints. This is the first report I've seen of that. Recommend investigating with wireshark. > I capture my data with netcat script (I call it netlog): > > #!/bin/bash > echo "You should now run in another window: tail -f $HOME/log" > while true; do > /bin/nc -u -l -p 6666 >> $HOME/log > done > > This also just doesn't work if I run the nc manually without a redirect: > > while true; do /bin/nc -u -l -p 6666; done That really shouldn't make any difference. -- http://selenic.com : development and support for Mercurial and Linux -- 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/