Bug 11016 - 4_a1: shutdown timer of +1 minute is too long
Summary: 4_a1: shutdown timer of +1 minute is too long
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-16 01:59 CEST by Bit Twister
Modified: 2015-04-28 02:41 CEST (History)
3 users (show)

See Also:
Source RPM: systemd-206-5.mga4.src.rpm
CVE:
Status comment:

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

Description Bit Twister 2013-08-16 01:59:13 CEST 
Description of problem:

shutdown timer of +1 minute is too long.
Currently cups has a problem of not telling systemd it is stopped.
As a result system hangs for a little more than a minute.

Snipped date, domain from journalctl log:
18:39:20 wb systemd[1]: Stopping CUPS Printing Service...
18:40:50 wb systemd[1]: cups.service stopping timed out. Killing.
18:40:50 wb systemd[1]: cups.service: main process exited, code=killed, status=9/KILL
18:40:50 wb systemd[1]: Unit cups.service entered failed state.
18:40:50 wb systemd[1]: Starting CUPS Printing Service...
18:40:50 wb systemd[1]: Started CUPS Printing Service.

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. click up a terminal
2. su - root
3. journalctl -fa
4. click up another root terminal
5. systemctl restart cups



Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-08-17 17:08:34 CEST

CC: (none) => mageia

David Walser 2013-08-21 00:06:33 CEST

CC: (none) => thierry.vignaud

Bit Twister 2014-01-18 16:33:01 CET

CC: (none) => junknospam

Comment 1 Bit Twister 2015-04-28 02:41:52 CEST 
no delay seen on 5 RC.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.