--nextPart20893152.N50vRlBT5c
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On Wednesday 09 September 2009 22:00:57 David Faure wrote:
> Coming back to this old thread after losing some configuration in kmail a=
nd
> plasma after a disk full situation....

>=20
> That's fine. We just want to know if something fails, whether that's
>  write() or flush().

I've been looking at the losing configuration problem (suffered several=20
times), and looked at KSaveFile.
In my modest opinion, the problem is not in KSaveFile, but in KConfig write=
()s=20
to the KSaveFile temporary file, where the returned number of bytes writed =
is=20
never checked against the expected bytes to be writen, and therefore there =
is=20
no way to detect the out of space condition, unless the signal SIGXFSZ is=20
handled.

Looked at:
http://www.opengroup.org/onlinepubs/000095399/functions/write.html

Regards.

--nextPart20893152.N50vRlBT5c
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAkqoEgIACgkQGTEZaQL1skiPuwCeNBwmNsH/Gpbvw2hIQRyjwHz6
B3oAnRqM5FbzaF/RMD0wmaIKfSVpR1Gr
=bWWS
-----END PGP SIGNATURE-----

--nextPart20893152.N50vRlBT5c--