Am 28.11.2018 um 06:26 schrieb Ryan C. Gordon:
>
>> Cool, I know how to fix this now, thank you!
>
> This is now fixed in upstream PhysicsFS here for the 3.0 branch:
>
> https://hg.icculus.org/icculus/physfs/rev/c17f025e7a92
>
> ...and here for the default (what will eventually become an
Cool, I know how to fix this now, thank you!
This is now fixed in upstream PhysicsFS here for the 3.0 branch:
https://hg.icculus.org/icculus/physfs/rev/c17f025e7a92
...and here for the default (what will eventually become an unstable
3.1.0) branch...
I tried this and can confirm that removing setBuffer calls avoids the
fsyncs. I verified this with strace too, which should be doable on any
machine (just "strace -o /tmp/output ./neverball", and after playing
check that /tmp/output contains no fsync calls).
Cool, I know how to fix this now,
On Tue, 16 Oct 2018 11:32:34 -0400 "Ryan C. Gordon" wrote:
>
> Can someone humor me and make a quick change to Neverball for me?
>
> In neverball/share/fs_physfs.c, there are three calls to
> PHYSFS_setBuffer(). Just comment them out and rebuild Neverball with
> PhysicsFS support and see if
Hi Ryan,
On Tue, 16 Oct 2018 11:32:34 -0400 "Ryan C. Gordon"
wrote:
>
> Can someone humor me and make a quick change to Neverball for me?
>
> In neverball/share/fs_physfs.c, there are three calls to
> PHYSFS_setBuffer(). Just comment them out and rebuild Neverball with
> PhysicsFS support
This is not actionable by Debian itself.
(But if you don't mind, we'll organize on this bug report briefly to get
this fixed upstream. Apologies in advance for a few emails worth of
extra chatter!)
--ryan.
Can someone humor me and make a quick change to Neverball for me?
In neverball/share/fs_physfs.c, there are three calls to
PHYSFS_setBuffer(). Just comment them out and rebuild Neverball with
PhysicsFS support and see if the problem goes away on the machine with
the slow disk.
I suspect I
7 matches
Mail list logo
