Bug 1070416 - `systemctl start' returns 0 despite not starting anything
Summary: `systemctl start' returns 0 despite not starting anything
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: rawhide
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Carlos O'Donell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-26 18:59 UTC by Siddhesh Poyarekar
Modified: 2016-11-24 12:13 UTC (History)
12 users (show)

Fixed In Version: glibc-2.19.90-4.fc21
Clone Of: 1048123
Environment:
Last Closed: 2014-09-29 11:37:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Siddhesh Poyarekar 2014-02-26 18:59:14 UTC
Currently the nscd service is installed in systemd as a simple service, which means that it is able to handle its own errors and does not quit.  Since nscd does not fit that description, i.e. it can exit on errors like, say, failing to parse nscd.conf, it should be declared as forking instead.

Comment 1 Siddhesh Poyarekar 2014-09-29 11:36:58 UTC
I fixed this some time ago.  The commit below is in Fedora glibc:

commit bdbcf83e8290d12c43b8740edd63e7cb7abd38dd
Author: Siddhesh Poyarekar <siddhesh>
Date:   Thu Feb 27 00:31:15 2014 +0530

    Use nscd service files from glibc sources and make the service forking
    
    Currently the nscd service is installed in systemd as a simple
    service, which means that it is able to handle its own errors and does
    not quit.  Since nscd does not fit that description, i.e. it can exit
    on errors like, say, failing to parse nscd.conf, it should be declared
    as forking instead.


Note You need to log in before you can comment on or make changes to this bug.