clear_tmp_enable="YES" conflicts with 'security/kstart'

Marin Bernard lists at olivarim.com
Thu Feb 14 21:56:04 UTC 2019


Hi,

We use security/kstart to maintain a local cache of kerberos tickets on our hosts. The tickets are stored in temporary caches files from the /tmp directory.

On 2018-02-07, a PR was committed to the security/kstart port to "move k5start higher up in the service start list". This change introduced a regression when the host is also configured to clear the /tmp dir at startup (clear_tmp_enable="YES"): the /tmp directory is cleaned *after* kstart is started, thus removing any managed kerberos cache file.

I do not know why the rc script was amended in the first place. Could someone give me some insight ? Clearing /tmp is a mandatory requirement for us because of the Kerberos context: is it possible to revert the rc script to its previous revision or propose anything else to fix this issue?

Thanks,

Marin.


More information about the freebsd-ports-bugs mailing list