Coraid's vblade is now on version 14. Gentoo's portage contains version 10. After looking at the code and ebuild I made minor changes in the ebuild (the source seems to be a tgz now and not a tar.gz and I'm not sure if my way is the best way to handle this). I have also included a fix for bug #137016 (this fix referenced in that bug). The new ebuild has been installed/uninstalled and I have performed the following basic testing: 1. exported two devices and mounted them remotely 2. started both devices and stopped one to ensure the init script is working All seems to "work well for me". WRT the init script... The source of the original problem was that the stop script did not check for the specific exported version, even though the ${@} was supposed to perform this function. My fix is simple, but I'm not sure that this is the correct way to fix the problem. As with jabberd2 a while back, having a Gentoo init script call a bash script which wraps the launch is probably a bad idea. We don't really have fine grained control over the vblade process because it's parent process is a bash shell. It's hard to ensure error control IMHO.
Created attachment 105394 [details] version 14 ebuild - initial submission not really much changed except in name from v10 ebuild
Created attachment 105395 [details] fix to init stop script fixing bug #137016
in cvs.
