On 2014-10-07 19:07, Neto, Antonio Jose Rodrigues wrote:
I found what is happening
If I use a non absolute path it works: the remote config should be on the
same directory with fio
Nossa Senhora:fio.patch neto$ ./fio --client 10.61.109.151 --remote-config
conf3
If I specify an absolute path, it does not work
Nossa Senhora:fio.patch neto$ ./fio --client 10.61.109.151 --remote-config
/root/fio.patch/conf3
hostname=s1, be=0, 64-bit, os=Linux, arch=x86-64, fio=fio-2.1.13-31-g15e3,
flags=1
Do you think we could fix it to make sure we can use --remote-config with
an absolute path?
That's very odd, there should be nothing special about it. If I do this:
axboe@lenny:/home/axboe/git/fio $ stat /root/x.fio
stat: cannot stat ‘/root/x.fio’: Permission denied
$ ./fio --client=localhost --remote-config /root/x.fio
and run
axboe@lenny:/home/axboe/git/fio $ sudo strace -o x -f ./fio --server
fio: server listening on 0.0.0.0,8765
and then look at the x strace output file, it all looks fine:
28632 recvfrom(4, "\v\0\1\0/root/x.fio", 15, MSG_WAITALL, NULL, NULL) =
15
28632 open("/root/x.fio", O_RDONLY) = 5
which is all find and dandy. Fio just passes the string of the filename,
and the server just does an fopen on that passed in file. So please run
the same experiment on your end with an strace of the server and the
arguments you used on the client, I'd like to see that.
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
