bin/syncio.sh missing
-
I'm going through the 3.3t release notes and saw the mention of bin/syncio.sh. After upgrade from 3.3s to 3.3t, I don't have that file. It's just in ustub. Is the tailoring code in the upgrade supposed to copy it to bin? Wonder if anyone else encountered this.
-
Same goes for bin/localenv.x.
-
For me on 3t, the syncio script is there and runs, but fails to produce a time.
I notice there is a new thing on the Main dashboard for IO "Sync IO" which I assume is related. No values in the chart yet. -
@rohan I managed to get the syncio.sh script to collect data into the syncio.log file and successfully populate the online charts.
Had to tweak the command line in syncio.sh which actually runs the bigrow.
I have also added a cron job to run syncio.sh regularly. I'm using the directory name, which I want to measure, as a parameter to syncio.sh in the cron command.
I'm sure Tom will update the script at some point. -
@rohan what did you need to change? We have found some unexpected OS and shell dependent issues with the "time" command.
-
The tailoring script is supposed to copy the contents of ustub to bin. So something must have gone wrong. pt3inst.err or pt3inst.log might reveal what.
I have found that I sometimes just need to run the install twice. I think I might have done something silly like replace the running pt3inst.sh while it is running.
-
Tom I just had to change ${TIMECMD} to the literal "time -p" without the quotes.
I couldn't get it to work any other way still using the time command.
You could avoid using the time command, but then you are getting away from the traditional method, which may give different results. -
@rohan That's helpful, thanks!
-
Just came across a case with a new CentOS VM where "time" wasn't installed. syncio.sh didn't do much of anything, just exiting pretty much immediately.
which timedidn't find a time command.Upshot: I installed
timeand then syncio.sh worked as expected.The code that sets TIMECMD may need to be a little more robust.
