On 22 Nov 2009 at 13:50, guy keren wrote: > > if you get SIGSEGV - most likely we have some memory ocrruption - so > catching this signal, flushing the log and then returning (letting the > process continue execution) is a big no-no.
Well, depending on buffering, flushing the log may be a good idea. The question whethet it's safe to continue is a valid one, however. You could abort after that. Maybe it's better to ensure htat the logs are flushed frequent enough, so you don't need this. (I haven't checked) Ulrich -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.