[Pidgin] #5597: Pidgin calls fsync far too often.

[Pidgin]

#5597: Pidgin calls fsync far too often.
------------------------+---------------------------------------------------
  Reporter:  neuron     |       Owner:  seanegan     
      Type:  defect     |      Status:  new          
  Priority:  minor      |   Milestone:               
 Component:  libpurple  |     Version:  2.4.1        
Resolution:             |    Keywords:  io fsync ext3
   Pending:  0          |  
------------------------+---------------------------------------------------
Comment (by elb):

 We probably should limit this to configuration files, if it's being called
 for other purposes.  For configuration files (which I suspect is actually
 the problem -- we write a lot of stuff ''way'' too often!), I don't know
 exactly what to do.  I agree that the corruption problem is, in general, a
 filesystem issue, and not something we should have to work around.
 However, it does seem to hit a lot of people (for whatever reason).

 Restricting the more draconian checks to win32 seems fine to me.  The bare
 fsync, however, probably should stay.  A better long-term solution might
 be to move the really chatty things (caches of buddy state information
 like remote aliases, window positions, etc.) to separate files which are
 designed to tolerate corruption more ably.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/5597#comment:4>
Pidgin <http://pidgin.im>
Pidgin