Re: [Iscsitarget-devel] what happens to the initiator when werestart ietd?

[Ross S. W. W. <rw...@me...>]

> -----Original Message-----
> From: Arne Redlich [mailto:ag...@po...] 
> 
> "Ross S. W. Walker" <rw...@me...> writes:
> 
> >> -----Original Message-----
> >> From: isc...@li... 
> >> [mailto:isc...@li...] On 
> >> Behalf Of Arne Redlich
> >> 
> >> That's what "ietadm --delete" initiates (yes, it needs to be 
> >> called before
> >> killing the daemon).
> >
> > We could also add a TERM trap to ietd that does the same 
> thing negating
> > the need to perform an ietadm --delete, or supplementing it...
> 
> I actually happen to like Vlad's approach of handling it in 
> the control
> dev's release() method - this way even a segfault in ietd 
> could be caught
> gracefully.

Not familiar with that, you have an idea on a simple implementation?

-Ross

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.