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] New: nscd: No such file or directory
Date: Wed, 13 Apr 2022 02:34:47 +0000	[thread overview]
Message-ID: <bug-29051-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29051

            Bug ID: 29051
           Summary: nscd: No such file or directory
           Product: glibc
           Version: 2.35
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: nscd
          Assignee: unassigned at sourceware dot org
          Reporter: mingli.yu at windriver dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

run 32-bit nscd in 64 bit env.
# 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

We acutally have the file like /etc/nsswitch.conf, but it turns out to check
/nsswitch.conf, more details as below.

# 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-03-17 08:08:29 UTC; 9s ago
Process: 388 ExecStart=/usr/sbin/nscd (code=exited, status=0/SUCCESS)
Main PID: 389 (nscd)
Tasks: 10 (limit: 4915)
Memory: 1.2M
CGroup: /system.slice/nscd.service
└─389 /usr/sbin/nscd

Mar 17 08:08:29 intel-x86-64 nscd[389]: 389 stat failed for file
`/nsswitch.conf'; will try again later: No such file or directory
Mar 17 08:08:29 intel-x86-64 nscd[389]: 389 disabled inotify-based monitoring
for file `/nsswitch.conf': No such file or directory
Mar 17 08:08:29 intel-x86-64 nscd[389]: 389 stat failed for file
`/nsswitch.conf'; will try again later: No such file or directory
Mar 17 08:08:29 intel-x86-64 nscd[389]: 389 disabled inotify-based monitoring
for file `/nsswitch.conf': No such file or directory
Mar 17 08:08:29 intel-x86-64 nscd[389]: 389 stat failed for file
`/nsswitch.conf'; will try again later: No such file or directory
Mar 17 08:08:29 intel-x86-64 systemd[1]: Started Name Service Cache Daemon.
Mar 17 08:08:30 intel-x86-64 nscd[389]: 389 disabled inotify-based monitoring
for file `/nsswitch.conf': No such file or directory
Mar 17 08:08:30 intel-x86-64 nscd[389]: 389 disabled inotify-based monitoring
for file `/nsswitch.conf': No such file or directory
Mar 17 08:08:30 intel-x86-64 nscd[389]: 389 disabled inotify-based monitoring
for file `/nsswitch.conf': No such file or directory
Mar 17 08:08:30 intel-x86-64 nscd[389]: 389 disabled inotify-based monitoring
for file `/nsswitch.conf': No such file or directory

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-04-13  2:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  2:34 mingli.yu at windriver dot com [this message]
2022-04-14  3:08 ` [Bug nscd/29051] " mingli.yu at windriver dot com
2022-06-13 11:03 ` 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@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: link
Be 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).