From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-yw0-f172.google.com ([209.85.161.172]:35930 "EHLO mail-yw0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750766AbdIELYW (ORCPT ); Tue, 5 Sep 2017 07:24:22 -0400 MIME-Version: 1.0 In-Reply-To: <20170905104641.GA8034@eguan.usersys.redhat.com> References: <1504104706-11965-1-git-send-email-amir73il@gmail.com> <1504104706-11965-8-git-send-email-amir73il@gmail.com> <20170905104641.GA8034@eguan.usersys.redhat.com> From: Amir Goldstein Date: Tue, 5 Sep 2017 14:24:20 +0300 Message-ID: Subject: Re: [PATCH v2 07/14] fsx: add optional logid prefix to log messages Content-Type: text/plain; charset="UTF-8" Sender: fstests-owner@vger.kernel.org To: Eryu Guan Cc: Josef Bacik , "Darrick J . Wong" , Christoph Hellwig , fstests , linux-xfs List-ID: On Tue, Sep 5, 2017 at 1:46 PM, Eryu Guan wrote: > On Wed, Aug 30, 2017 at 05:51:39PM +0300, Amir Goldstein wrote: >> When writing the intermixed output of several fsx processes >> to a single log file, it is usefull to prefix logs with a log id. >> Use fsx -j to define the log messages prefix. > > Would it be better to allow any string as prefix, not limit to id > number? > Maybe, but I didn't see an immediate need for that beyond the concurrent test runs, for with numeric id is sufficient. Besides, the function that prepends the prefix, prt() is sometimes uses for continued line, which results with weird looking lines like this one: 1: 60( 60 mod 256): 1: FALLOC 0x30140 thru 0x30f3c (0xdfc bytes) 1: EXTENDING1: So it's not really worth fixing properly, but anything more then a single numeric prefix is going to look quite bad.