Issue 20385 - Q-PCD Quality-2 [Signal Handling]
Summary: Q-PCD Quality-2 [Signal Handling]
Status: ACCEPTED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.1
Hardware: Other Other OS
: P5 (lowest) Trivial (vote)
Target Milestone: AOO Later
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-29 20:30 UTC by matthias.huetsch
Modified: 2013-02-07 22:13 UTC (History)
1 user (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description matthias.huetsch 2003-09-29 20:30:22 UTC 
Source
Experienced Unix User

Category
Stability

Customer Need/Problem
If SO/OOo is hung under Unix, you have only one chance to kill it properly (to
preserve work): you can send a SIGABRT or SIGSEGV to cause it to save files
that have been edited into the crash recovery area.

Product Requirement 
More obvious signal choice, and increased number of signals, to gracefully
terminate SO/OOo. First and foremost SIGHUP should cause this graceful
termination, as should other signals like SIGTERM and SIGQUIT.

Comment
-

Eng Effort
-

Eng Owner
Matthias Huetsch

Product Concept
1) The SO signal handling code needs to be fixed: a) for proper handling of
asynchronously delivered signals to a multithreaded process, and b) for proper
cooperation with an in-process Java Virtual Machine or other possibly
conflicting runtime environments.
2) The chosen graceful termination signals (HUP, QUIT, TERM) then need to be
propagated to and interpreted appropriately by the SO Application Framework.

Functional Specification
-
Comment 1 matthias.huetsch 2003-09-29 20:31:39 UTC 
Accepting...
Comment 2 lutz.hoeger 2003-10-23 07:42:38 UTC 
added keyword Q-PCD
Comment 3 Martin Hollmichel 2004-05-28 15:10:42 UTC 
according to the announcement on releases
(http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=7503) this issue
will be re-targeted to OOo Later.