On Wed, 2012-06-13 at 14:11 -0400, Simo Sorce wrote: > On Wed, 2012-06-13 at 12:18 -0400, Stephen Gallagher wrote: > > > Also, I'm going to open a bug to have pam_systemd.so create a > > subdirectory for us, so we're not polluting the /run/user/username > > directory with cryptically-named files. > > Why cryptically named files ?
libkrb5 creates files named tktXXXXX (where XXXXX is random) and primary in the target directory. I'd like to keep this in a subdirectory of /run/user/username. > > We should just create one well know ccache dir. > And we can create it ourselves, why should we have pam_systemd involved > here ? /run/user/username is created automatically by pam_systemd during session start (and removed on last session exit). If we decide to take on directory creation, we need to handle parent directories too (in case someone chooses to manually set a cache dir that's much deeper). And this still wouldn't play well with other libkrb5-using applications, since they would each need to grow this functionality as well. So I opened https://bugzilla.redhat.com/show_bug.cgi?id=831738 to have pam_systemd just do this for us on session login so we don't have to worry about it for each and every potential consumer. I also opened https://bugzilla.redhat.com/show_bug.cgi?id=831740 for the record (to change to /run/user/UID instead of /run/user/username). We'll see where that goes.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ sssd-devel mailing list sssd-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/sssd-devel
