New version with config file in /etc/conf.d Reproducible: Always Steps to Reproduce: not a bug
Created attachment 170162 [details] app-crypt/kstart/kstart-3.14-r2.ebuild
Created attachment 170163 [details] k5start.confd
Created attachment 170165 [details] k5start.initd
Hi! What do you need the k5start as daemon for? Is it advisable to have a permanent ticket after startup? I see some danger for abuse if we provide an init script. Discussion is welcome ... greets, mueli
Created attachment 170248 [details] app-crypt/kstart-3.14-r2.ebuild
I have a client pc mounting /home and /data duringe the boot. I need root access because the client make a backup of /data. I only modify the init.d script using separate file in /etc/conf.d so in the future i don't need to modify the init script after every update.
Created attachment 173828 [details] init.d script file changed from need mit-krb5kdc in before mit-krb5kdc
Possible of course, but usual/traditional way to use kstart is through cron. I am going to close this as WONTFIX.