Bug 33196 - Notification of SIGTERM/SIGKILL should be adapted
Summary: Notification of SIGTERM/SIGKILL should be adapted
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: UMC - Process overview
Version: UCS 3.2
Hardware: Other Linux
: P5 enhancement
Target Milestone: UCS 3.2-x
Assignee: UMC maintainers
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-07 14:03 CET by Dirk Wiesenthal
Modified: 2017-08-08 07:11 CEST (History)
3 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Usability
Customer ID:
Max CVSS v3 score:

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

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Wiesenthal univentionstaff 2013-11-07 14:03:04 CET 
Now that notifications are persistent, they should include the name of the process or something similar because otherwise the notification history is not very helpful.
Comment 1 Erik Damrose univentionstaff 2013-11-07 14:30:39 CET 
I think the concept of 'one-time' messages is better, see also Bug 32997#c1
Comment 2 Dirk Wiesenthal univentionstaff 2013-11-07 15:39:25 CET 
Same holds for Services module ("Stopped successfully"). But 'one-time' messages are a good idea.
Comment 3 Dirk Wiesenthal univentionstaff 2013-11-08 16:05:07 CET 
And for Quota module (Quota activated)
Comment 4 Stefan Gohmann univentionstaff 2017-06-16 20:39:16 CEST 
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 5 Stefan Gohmann univentionstaff 2017-08-08 07:11:09 CEST 
This issue has been filed against UCS 3.2.

UCS 3.2 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.