Default libkrb5 ccache location

[Lennart Poettering]

On Tue, 30.07.13 08:36, Stephen Gallagher (sgallagh at redhat.com) wrote:

> On 07/29/2013 06:50 PM, Lennart Poettering wrote:
> > On Mon, 29.07.13 17:25, Simo Sorce (simo at redhat.com) wrote:
> >> If need be we can add a scanning cron job (or daemon or whatever)
> >> that will walk through the caches and eliminate those that have
> >> expired credentials in them, it wouldn't be too hard to add, just
> >> a matter of spending some time on the binary that check this data
> >> in a 'safe' way.
> > 
> > Well, tmpfiles does that on /tmp already.
> > 
> 
> While I appreciate the intent of tmpfs on /tmp, it's pretty much a
> guarantee that anyone running a server who knows about it will shut it
> off because it causes more problems than it solves when using
> applications like MySQL, which stores a lot of data in /tmp, thus
> resulting in massive swapping and slowing the entire system down.
> 
> We need a solution that is consistently tmpfs here.

Well, if MySQL still has that limitation, then it should be fixed. Fix
problems where they are, don't work around them.

Also, writing things via tmpfs into swap to disk, or directly to disk is
not that much of a difference.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.