Waldo Bastian wrote:
> 
> On Sun, 02 Jul 2000, Mirko Sucker wrote:
> > Waldo Bastian wrote:
> > > On Fri, 30 Jun 2000, Sergey Zhitomirsky wrote:
> > > > Full output :
> > > >
> > > > [szh@szh szh]$ kmail
> > > > entering KMKernel::init()
> > > > kmail: AddressBook::reloaded: file has been reloaded.
> > > > kmail: AddressBook::updateMirrorMap: updating mirror map.
> > > > kmail: AddressBook::updateMirrorMap: done, no file loaded.
> > > > kmail: AddressBook::reloaded: file has been reloaded.
> > > > kmail: AddressBook::updateMirrorMap: updating mirror map.
> > > > kmail: AddressBook::updateMirrorMap: done.
> > > > kmail: AddressBook::updateMirrorMap: updating mirror map.
> > > > kmail: AddressBook::updateMirrorMap: done.
> > > > kmail: QConfigDB::save: saving database
> > > > -->/home/szh/.kde/share/apps/kab/addressbook.kab. backup<--.
> > >
> > > Why does KAB always write out a database? Startup of KAB takes way too
> > > much time IMO. The goal for applications should be too start up within
> > > 0.3 seconds.
> >
> > Do you know what users shout at me if a simple bug destroys there address
> > database?
> 
> We have the same problem with configuration files. Still, we don't start to
> make backup files of every configuration file during startup. I'm sure you
> had a reason to do what you are doing, that doesn't mean the current way of
> doing is necasserily the best.
> 
> > ....
> > But there will be a feature in the configuration to disable backup
> > creation. Does anybody opt to disable it by default? I would opt for
> > enabling it.
> 
> I have no problem with backups. I have a problem with backups which are made
> unnecasserily. I never touch my addressbook and yet, every time kmail starts,
> a backup is made???? What is that good for?

Peace of mind? I would far rather have a million backups than a single
disaster.

Rich.

> 
> Cheers,
> Waldo
> --
> Make way, KDE/Linux is coming to a desktop near you!

-- 
     Richard Moore		rich@ipso-facto.freeserve.co.uk
http://www.robocast.com/	richard@robocast.com
http://developer.kde.org/	rich@kde.org