From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22946 invoked by alias); 23 Jun 2011 12:45:35 -0000 Received: (qmail 22939 invoked by uid 22791); 23 Jun 2011 12:45:35 -0000 X-SWARE-Spam-Status: No, hits=-6.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 23 Jun 2011 12:45:18 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p5NCjHWr019658 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 23 Jun 2011 08:45:17 -0400 Received: from localhost (vpn1-5-79.ams2.redhat.com [10.36.5.79]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p5NCjGQK026103; Thu, 23 Jun 2011 08:45:17 -0400 Date: Thu, 23 Jun 2011 12:45:00 -0000 From: "Richard W.M. Jones" To: Josh Stone Cc: systemtap@sourceware.org Subject: Re: Flushing systemtap output without restarting (was: Re: Rapidly running systemtap causing hangs or oops) Message-ID: <20110623124516.GI18438@amd.home.annexia.org> References: <20110622230025.GG18438@amd.home.annexia.org> <4E028028.4010603@redhat.com> <20110623075126.GJ803@amd.home.annexia.org> <20110623101217.GH18438@amd.home.annexia.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110623101217.GH18438@amd.home.annexia.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2011-q2/txt/msg00321.txt.bz2 On Thu, Jun 23, 2011 at 11:12:17AM +0100, Richard W.M. Jones wrote: > It certainly looks like they run asynch, because my actual output > (sometimes) looks like: > > 1308822714.015994546: mount > 1308822714.424888519: mount > 1308822714.43626: module("ext2").statement("ext2_mount@fs/ext2/super.c:1378") > 1308822714.43634: module("ext2").statement("ext2_mount@fs/ext2/super.c:1379") > 1308822714.442957: module("ext2").statement("ext2_mount@fs/ext2/super.c:1378") > 1308822714.442965: module("ext2").statement("ext2_mount@fs/ext2/super.c:1379") Damn, it's the stupidest mistakes which are the easiest to overlook. In fact the ordering (by time) is *correct*. It just appears wrong because I didn't format the microsecond field with leading zeroes (%06d) ... Thanks everyone, I will keep going down the timestamp route. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top