This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: nscd messages

To: Thorsten Kukuk <kukuk at suse dot de>
Subject: Re: nscd messages
From: Ulrich Drepper <drepper at redhat dot com>
Date: 17 Jul 2001 11:13:49 -0700
Cc: libc-hacker at sourceware dot cygnus dot com
References: <m3elrgml06.fsf@otr.mynet> <20010717105426.A17603@suse.de>
Reply-To: drepper at cygnus dot com (Ulrich Drepper)

Thorsten Kukuk <kukuk@suse.de> writes:

> All I can see is that you don't print messages now where I would
> say this are all real error messages where the sysadmin should
> look from where it comes.

Where?  As the ChangeLog comment mentions, all these are problems
caused by the user application.  For instance, if the version number
doesn't match this is a deliberate attempt to disturb the program.
With debugging all is still visible.

> I cannot find any messages in our log files here from nscd.

I get tons of messages.  Whenever you have a program with is stop in
the middle of a transfer nscd will complain.

> Everybody can send messages to syslog, I don't see this as problem.

That's something which can and should be handled separately.  I don't
know why there are no ACLs or so.  Maybe newer, more secure versions
have it.

-- 
---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------

References:
- nscd messages
  - From: Ulrich Drepper
- Re: nscd messages
  - From: Thorsten Kukuk

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]