All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Frank Filz <ffilzlnx@mindspring.com>
Cc: Rupert Dance <rsdance@soft-forge.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Connectathon Issues
Date: Thu, 19 Mar 2015 11:04:21 -0400	[thread overview]
Message-ID: <550AE575.4000104@RedHat.com> (raw)
In-Reply-To: <64DCD95C-CD5C-4A16-B6EC-49661576C466@mindspring.com>



On 03/17/2015 09:26 PM, Frank Filz wrote:
> There is a patched cthon04 out there. I think from Jeff Layton. 
> 
> Frank
> 
> Sent from my iPhone
> 
> On Mar 17, 2015, at 3:35 PM, Steve Dickson <SteveD@redhat.com> wrote:
> 
>> On 03/17/2015 03:15 PM, Rupert Dance wrote:
>>> Nroff
>>>
>>> ./stat: no data in nroff.time
>> I believe this has to do with the format of time 'time' command.
>> stat.c expects a particular date format that changes whether 
>> /usr/bin/time is used or the shell version of data. 
>>
>> try adding TIME=/usr/bin/time to the top of general/runtests.wrk
Taking a closer look there is code that is commented out that 
will solve this problem.

# if the default time command doesn't return the right format,
# you may have to use the following lines
#case `uname` in
#[lL]inux*)
#   TIME=/usr/bin/time
#   ;;
#*)
#   TIME=/bin/time
#   ;;
#esac
#if [ ! -f $TIME ]
#then
#   TIME=/usr/bin/time
#   if [ ! -f $TIME ]
#   then
#       echo "Where is the time command?"
#       exit 1
#   fi
#fi

Maybe its time to uncomment it... 

steved.


  reply	other threads:[~2015-03-19 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <009501d060e6$b54c3780$1fe4a680$@soft-forge.com>
2015-03-17 22:35 ` Connectathon Issues Steve Dickson
2015-03-18  1:26   ` Frank Filz
2015-03-19 15:04     ` Steve Dickson [this message]
2015-03-19 16:57       ` Rupert Dance
2015-03-26 17:19         ` Steve Dickson
2015-03-26 17:57           ` Chuck Lever
2015-03-27 19:00             ` Rupert Dance

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=550AE575.4000104@RedHat.com \
    --to=steved@redhat.com \
    --cc=ffilzlnx@mindspring.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rsdance@soft-forge.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.