--nextPart11384589.U0VtYHzNak
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Thorsten Zachmann wrote:
>how about using a mutex that will also catch the case where the umask is
>changed while the program is running?

I prefer your earlier idea (getting the umask at program start). Reasons=20
why:

1) mutexes are expensive
2) you protect only KTemporaryFile, but *ALL* other file creations in=20
other threads (QFile, creat(2), open(2), QTemporaryFile, Unix sockets) go=20
unchecked
3) it's highly unlikely that anyone changes the umask during the program=20
execution anyways. (but they do create files)

=2D-=20
=A0 Thiago Macieira =A0- =A0thiago (AT) macieira.info - thiago (AT) kde.org
=A0 =A0 PGP/GPG: 0x6EF45358; fingerprint:
=A0 =A0 E067 918B B660 DBD1 105C =A0966C 33F5 F005 6EF4 5358

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQBH6/2QM/XwBW70U1gRAjW8AJ92hCKecX1CEhV4vVIzfD04GQItggCgtqfE
EBATcZb1qATEbovPoPm4jsc=
=NqJK
-----END PGP SIGNATURE-----

--nextPart11384589.U0VtYHzNak--