public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mingli.yu at windriver dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nscd/29051] nscd: No such file or directory Date: Thu, 14 Apr 2022 03:08:44 +0000 [thread overview] Message-ID: <bug-29051-131-v2ZOEORe7j@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29051-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29051 --- Comment #1 from Mingli <mingli.yu at windriver dot com> --- BTW, it works with glibc 2.34. The issue comes out after upgrade glibc to 2.35 # rpm -qa | grep nscd lib32-nscd-2.34-r0.corei7_32 # rpm -ql lib32-nscd /etc /etc/nscd.conf /etc/tmpfiles.d /etc/tmpfiles.d/nscd.conf /lib /lib/systemd /lib/systemd/system /lib/systemd/system-preset /lib/systemd/system-preset/98-lib32-nscd.preset /lib/systemd/system/nscd.service /usr /usr/sbin /usr/sbin/nscd /var /var/db /var/db/nscd # cat /lib/systemd/system/nscd.service # systemd service file for nscd [Unit] Description=Name Service Cache Daemon [Service] Type=forking ExecStart=/usr/sbin/nscd ExecStop=/usr/sbin/nscd --shutdown ExecReload=/usr/sbin/nscd -i passwd ExecReload=/usr/sbin/nscd -i group ExecReload=/usr/sbin/nscd -i hosts ExecReload=/usr/sbin/nscd -i services ExecReload=/usr/sbin/nscd -i netgroup Restart=always PIDFile=/run/nscd/nscd.pid [Install] WantedBy=multi-user.target root@intel-x86-64:~# systemctl status nscd * nscd.service - Name Service Cache Daemon Loaded: loaded (/lib/systemd/system/nscd.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2022-04-14 03:06:05 UTC; 2min 25s ago Process: 181 ExecStart=/usr/sbin/nscd (code=exited, status=0/SUCCESS) Main PID: 183 (nscd) Tasks: 10 (limit: 3584) Memory: 900.0K CGroup: /system.slice/nscd.service `-183 /usr/sbin/nscd Apr 14 03:06:18 intel-x86-64 nscd[183]: 183 monitoring directory `/etc` (2) Apr 14 03:06:18 intel-x86-64 nscd[183]: 183 monitoring file `/etc/passwd` (1) Apr 14 03:06:18 intel-x86-64 nscd[183]: 183 monitoring directory `/etc` (2) Apr 14 03:06:18 intel-x86-64 nscd[183]: 183 monitoring file `/etc/nsswitch.conf` (6) Apr 14 03:06:18 intel-x86-64 nscd[183]: 183 monitoring directory `/etc` (2) Apr 14 03:06:18 intel-x86-64 nscd[183]: 183 monitoring file `/etc/group` (3) Apr 14 03:06:18 intel-x86-64 nscd[183]: 183 monitoring directory `/etc` (2) Apr 14 03:06:22 intel-x86-64 nscd[183]: 183 monitored file `/etc/resolv.conf` changed (mtime) Apr 14 03:06:22 intel-x86-64 nscd[183]: 183 monitoring file `/etc/resolv.conf` (7) Apr 14 03:06:22 intel-x86-64 nscd[183]: 183 monitoring directory `/etc` (2) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-14 3:08 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-13 2:34 [Bug nscd/29051] New: " mingli.yu at windriver dot com 2022-04-14 3:08 ` mingli.yu at windriver dot com [this message] 2022-06-13 11:03 ` [Bug nscd/29051] " schwab@linux-m68k.org 2022-06-14 1:59 ` mingli.yu at windriver dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-29051-131-v2ZOEORe7j@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).