Make Refuses to open symlinks msg less spurious
commite3eb1305f58f542d63eb08ee8b08ba055d6e88bb
authorNicolas Williams <nico@cryptonector.com>
Sat, 17 Aug 2013 04:46:06 +0000 (16 23:46 -0500)
committerNicolas Williams <nico@cryptonector.com>
Thu, 12 Sep 2013 17:14:39 +0000 (12 12:14 -0500)
tree21b38540e30138af1f3a13269d88914b89e21b0b
parent0866ee2615f779cd3262c65237ac13b1f38bde7c
Make Refuses to open symlinks msg less spurious

If we're racing enough we could complain about symlinks where there were
none.  This was very surprising.  Make it surprise less.

We should really #ifndef O_NOFOLLOW that code chunk too, for the obvious
reason that we don't need to worry about symlinks if we have and use
O_NOFOLLOW.

Also, since all uses of fcc_open() use O_NOFOLLOW we should move that
into fcc_open().  Ditto O_BINARY and O_CLOEXEC.
lib/krb5/fcache.c