This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nscd/16639] systemctl start nscd.service should return non-zero status on failure
- From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 10 Mar 2014 07:49:09 +0000
- Subject: [Bug nscd/16639] systemctl start nscd.service should return non-zero status on failure
- Auto-submitted: auto-generated
- References: <bug-16639-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16639
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The branch, master has been updated
via 8b4ff97413fc32ea7f817586bc682ff2cc34527b (commit)
from 54b46a4b3efd179ccbbf8e342e64391e2b590f1b (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=8b4ff97413fc32ea7f817586bc682ff2cc34527b
commit 8b4ff97413fc32ea7f817586bc682ff2cc34527b
Author: Siddhesh Poyarekar <siddhesh@redhat.com>
Date: Mon Mar 10 13:17:54 2014 +0530
Mark nscd service as forking in systemd service file (BZ #16639)
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.
-----------------------------------------------------------------------
Summary of changes:
ChangeLog | 5 +++++
NEWS | 2 +-
nscd/nscd.service | 4 ++--
3 files changed, 8 insertions(+), 3 deletions(-)
--
You are receiving this mail because:
You are on the CC list for the bug.