Summary: | sys-block/open-iscsi - broken initscript | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Doktor Notor <notordoktor> |
Component: | New packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | base-system, craig, gentoo, premek, spamtrap+gentoo, staff |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 340425 | ||
Bug Blocks: | |||
Attachments: |
initscript patch
iscsid-init.d iscsid-conf.d iscsid-conf.d.patch iscsid-init.d.patch iscsid-init.d |
Description
Doktor Notor
2010-03-03 14:08:41 UTC
Created attachment 221933 [details, diff]
initscript patch
An additional problem is, if you use AUTOSTARTTARGETS="yes" it will "return $?", then the runscript system thinks that iscsid wasn't started, but the deamon is indeed still running. At that point, we could: - run stop(), disconnect from already connected targets, unload iscsi modules - ignore the error Maybe we could add AUTOSTART="strict" which will run stop(); otherwise the error should be ignored. Opinions? Created attachment 222547 [details]
iscsid-init.d
Created attachment 222549 [details]
iscsid-conf.d
Created attachment 222551 [details, diff]
iscsid-conf.d.patch
Created attachment 222553 [details, diff]
iscsid-init.d.patch
(In reply to comment #2) > Maybe we could add AUTOSTART="strict" which will run stop(); otherwise the > error should be ignored. +1 on this... no need to stop() otherwise. And yeah, good point, the problem you've described is annoying as well. Created attachment 249972 [details]
iscsid-init.d
InCVS. |