Le mardi 30 septembre 2008 à 21:26 +0200, Loïc Minier a écrit : > Sadly, gconfd/saved_state is still used for similar logging which is > used to restore listeners when gconfd restarts (AIUI).
> The log files is used in two ways: continuous logging happens all the > time, and will be used if the process dies badly, and if the process > gets the time to shutdown decently or for some signals, it will save > its state to a new file, and overwrite the logfile with this state > before exiting. > > I'd say that the open file, the continuous write to a real file (which > might spinup the hard disk IIUC or cause network IO as you point out) > is completely an obsolete use case, and we should simply rely on the > latter part of the saving process. > Perhaps we can propose that upstream. Add to that the fact this feature is here for the case where gconfd crashes unexpectedly, and that it is very stable nowadays, so that makes it quite useless. I’ll propose to remove it to upstream. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `- our own. Resistance is futile.
signature.asc
Description: Ceci est une partie de message numériquement signée
