The summary just about says it. It appears to be done very deliberately, but I can't think of a reason to install the binary in /etc/init.d. I think those two lines in the ebuild: exeinto /etc/init.d doexe ipvsadm should just come out. Reproducible: Always Steps to Reproduce:
sorry, that is mine ;)
I think that was supposed to be ipvsadm.sh which is a startup script. I went ahead and wrote a Gentoo'ized startup script for ipvsadm. Give the mirrors a while to update and then give it a try. I havent' bumped it yet, I want to get somebody else to test it. So let me know if it works okay for you.
You have a nasty typo in the stable ebuild now -- after exeinto /etc/init.d/ you have newbin ${FILESDIR}/ipvsadm-init ipvsadm which puts your runscript into /bin/ipvsadm, masking the real ipvsadm in /sbin. This needs fixin'! If anyone has a script running that calls ipvsadm without the full path and reinstalls for some reason, they'll be unhappy. Also, your init script, which you cloned from iptables, still refers to iptables where it means to say ipvsadm in an eerror message.
good catch, it's supposed to be newexe, fixed that and the init script in cvs
so we can close it ;)
