Bug#515653: fsync() based test version

2011-05-11 Thread Martin Steigerwald
Am Samstag, 19. März 2011 schrieb Thibaut VARENE: On Sat, Mar 19, 2011 at 5:47 PM, Martin Steigerwald mar...@lichtvoll.de wrote: Am Sunday 06 March 2011 schrieb Thibaut VARENE: Would you be kind enough to test it? I don't crash my systems as often as you do, and they're setup in a way that

Bug#515653: fsync() based test version

2011-05-11 Thread Thibaut VARENE
On Wed, May 11, 2011 at 8:48 PM, Martin Steigerwald mar...@lichtvoll.de wrote: So my approach failed. But I wonder whether your approach would have done more good than my daily backups, since uptimed doesn't do a regular backup of the configuration, but only on stopping it, maybe also on

Bug#515653: fsync() based test version

2011-05-11 Thread Martin Steigerwald
Am Mittwoch, 11. Mai 2011 schrieb Thibaut VARENE: On Wed, May 11, 2011 at 8:48 PM, Martin Steigerwald mar...@lichtvoll.de wrote: So my approach failed. But I wonder whether your approach would have done more good than my daily backups, since uptimed doesn't do a regular backup of the

Bug#515653: fsync() based test version

2011-03-19 Thread Martin Steigerwald
Am Sunday 06 March 2011 schrieb Thibaut VARENE: On Sun, Mar 6, 2011 at 6:52 PM, Martin Steigerwald mar...@lichtvoll.de wrote: Am Sunday 06 March 2011 schrieb Thibaut VARENE: As stated before, the correct solution would be to add another layer of checks during daemon startup, which would

Bug#515653: fsync() based test version

2011-03-19 Thread Thibaut VARENE
On Sat, Mar 19, 2011 at 5:47 PM, Martin Steigerwald mar...@lichtvoll.de wrote: Am Sunday 06 March 2011 schrieb Thibaut VARENE: Would you be kind enough to test it? I don't crash my systems as often as you do, and they're setup in a way that apparently makes it impossible for me to reproduce

Bug#515653: fsync() based test version

2011-03-19 Thread Martin Steigerwald
Am Saturday 19 March 2011 schrieb Thibaut VARENE: You wrote you build it already. Do you have that package still available? Then I'd test it after I am convinced that the fsync() based version does what it should. Well no, I don't have the test build anymore. Since you were able to test

Bug#515653: fsync() based test version

2011-03-06 Thread Thibaut VARENE
On Sat, Mar 5, 2011 at 4:22 PM, Martin Steigerwald mar...@lichtvoll.dewrote: Since after loosing uptime records once again due to a crash while testing kernels I am so through with it that it is not even funny anymore, Theodore T'so said that one should not fear the fsync() [1] - especially

Bug#515653: fsync() based test version

2011-03-06 Thread Martin Steigerwald
Am Sunday 06 March 2011 schrieb Thibaut VARENE: On Sat, Mar 5, 2011 at 4:22 PM, Martin Steigerwald mar...@lichtvoll.dewrote: Since after loosing uptime records once again due to a crash while testing kernels I am so through with it that it is not even funny anymore, Theodore T'so said that

Bug#515653: fsync() based test version

2011-03-06 Thread Thibaut VARENE
On Sun, Mar 6, 2011 at 6:52 PM, Martin Steigerwald mar...@lichtvoll.de wrote: Am Sunday 06 March 2011 schrieb Thibaut VARENE: As stated before, the correct solution would be to add another layer of checks during daemon startup, which would assert that the file it's reading is valid (i.e. to

Bug#515653: fsync() based test version

2011-03-06 Thread Thibaut VARENE
On Sun, Mar 6, 2011 at 9:05 PM, Thibaut VARENE vare...@debian.org wrote: On Sun, Mar 6, 2011 at 6:52 PM, Martin Steigerwald mar...@lichtvoll.de wrote: Am Sunday 06 March 2011 schrieb Thibaut VARENE: As stated before, the correct solution would be to add another layer of checks during daemon

Bug#515653: fsync() based test version

2011-03-05 Thread Martin Steigerwald
Since after loosing uptime records once again due to a crash while testing kernels I am so through with it that it is not even funny anymore, Theodore T'so said that one should not fear the fsync() [1] - especially not with Ext4 - and I prefer not loosing uptime records over and over and over