Request

  Could you please reincorporate the critical feature that 
  automatically saves modified documents when receiving an 
  signal into OOo 2.0, SO 8 and SS 8?

  OOo 1.1.x, SO 8 and SS 8 are capable to start the following 
  feature upon receipt of a signal such as 
  "kill -SEGV <process-id of soffice.bin>"

    "An unrecoverable error has occurred."
     All modified files have been saved and can 
     probably be recovered at program start."

  OOo 2.0 Beta2, however, seems not to have this useful 
  function. soffice.bin just ends with a core dump when it 
  receives a signal.


 Justification

  This feature really makes OOo, SO and SS reliable. Lack of 
  this type of function brings users a bad reputation about 
  our products telling Office 2003 is more reliable. 

  The Office has a similar feature "Microsoft Office Application 
  Recovery" under Start > All Programs > Microsoft Office > 
  Microsoft Office Tools.

  A town office in Japan has introduced a system of 60 Sun Ray 
  terminals running on Solaris 9 SPARC. Unfortunately, users 
  sometime face a frozen StarSuite 7 with modified documents on 
  their display when opening an Excel file. It is a bug in SS 7 
  and has been already fixed in OOo 1.9. 

  I have implemented a shell script that can be easily run by 
  simply choosing a menu item next to items of StarSuite under 
  the category Office in Gnome Start menu. The script is attached 
  in this issue and will give a user a choice like: 

  ==================================================================
   Do you really want to forcedly terminate StarSuite?
     1. Attempts to save unsaved documents and terminates StarSuite
     2. Terminates StarSuite anyway
     0. Cancel

   What would you like? Answer with a number : 
  ==================================================================

  Choice 1 will lead    "kill -SEGV <process-id of soffice.bin>"
  Choice 2 will execute "kill -KILL <process-id of soffice.bin>"

  OOo 2.0, SO 8 and SS 8 has employed an additional feature that 
  internally watches activities of soffice.bin and will fire an 
  emergency alarm when watch dog timer is over, and consequently 
  will start recovery process. 

  The feature, however, sometime does not help at all even though 
  soffice.bin looks frozen because the soffice.bin is running 
  without control, but with repeatedly resetting the watch dog 
  timer.

  Therefore, we still need this type of feature in OOo 2.0, SO 8 
  and SS 8 that manually terminates soffice.bin with saving 
  modified documents.