Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Bruce Cran <bruce@cran.org.uk>
To: Sitsofe Wheeler <sitsofe@yahoo.com>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: --server broken on Windows (2.1.1 and 2.0.14)
Date: Tue, 26 Nov 2013 11:01:04 +0000	[thread overview]
Message-ID: <52947F70.6000002@cran.org.uk> (raw)
In-Reply-To: <20131126063901.GA4631@sucs.org>

On 11/26/2013 6:39 AM, Sitsofe Wheeler wrote:
> The problem with waitpid when trying to connect to an fio in server mode
> as mentioned in http://www.spinics.net/lists/fio/msg02319.html from
> August still seems to be here with the prebuilt 2.1.1 Windows binaries
> on http://www.bluestop.org/fio/ . Additionally the Windows client seems
> to be unable to read job files when connecting to the server:
> ...
>
> Does anyone have any ideas?


I've implemented waitpid() and writev() in 2.1.4 and will build new 
binaries, but --server remains broken because fio uses fork() now and 
that's almost impossible to support on Windows without resorting to Cygwin.

-- 
Bruce Cran

  reply	other threads:[~2013-11-26 11:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26  6:39 --server broken on Windows (2.1.1 and 2.0.14) Sitsofe Wheeler
2013-11-26 11:01 ` Bruce Cran [this message]
2013-11-26 19:06 ` Bruce Cran

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=52947F70.6000002@cran.org.uk \
    --to=bruce@cran.org.uk \
    --cc=fio@vger.kernel.org \
    --cc=sitsofe@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox