Summary: | app-crypt/kstart - new revision with config file in /etc/conf.d | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michele Schiavo <micheleschi> |
Component: | New packages | Assignee: | Gentoo Kerberos Maintainers <kerberos> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
app-crypt/kstart/kstart-3.14-r2.ebuild
k5start.confd k5start.initd app-crypt/kstart-3.14-r2.ebuild init.d script file |
Description
Michele Schiavo
2008-10-28 22:15:12 UTC
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. |