First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 159994
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Robin Johnson <robbat2@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Sean Lynn <slynn@granite-mtn.net>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
vblade-14.ebuild version 14 ebuild - initial submission text/plain Sean Lynn 2007-01-04 09:30 0000 1.03 KB Details
init.d-vblade.vblade0 fix to init stop script fixing bug #137016 text/plain Sean Lynn 2007-01-04 09:31 0000 2.59 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 159994 depends on: Show dependency tree
Show dependency graph
Bug 159994 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-01-04 09:28 0000
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.

------- Comment #1 From Sean Lynn 2007-01-04 09:30:39 0000 -------
Created an attachment (id=105394) [edit]
version 14 ebuild - initial submission

not really much changed except in name from v10 ebuild

------- Comment #2 From Sean Lynn 2007-01-04 09:31:27 0000 -------
Created an attachment (id=105395) [edit]
fix to init stop script fixing bug #137016

------- Comment #3 From Robin Johnson 2007-03-07 19:50:04 0000 -------
in cvs.

First Last Prev Next    No search results available      Search page      Enter new bug