From owner-freebsd-bugs Wed Jul 21 8:36: 6 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id DEE06154D2 for ; Wed, 21 Jul 1999 08:36:03 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.8.8/8.8.8) with ESMTP id IAA04218; Wed, 21 Jul 1999 08:35:49 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <3795E8D5.CEABD4C4@gorean.org> Date: Wed, 21 Jul 1999 08:35:49 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mitch Collinsworth Cc: Dag-Erling Smorgrav , freebsd-bugs@FreeBSD.ORG, mkc@broccoli.graphics.cornell.edu Subject: Re: bin/12349: 3.2-R inetd doesn't re-read ALL configuration info at HUP signal References: <199907211445.AA031878326@broccoli.graphics.cornell.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mitch Collinsworth wrote: > > >mkc@graphics.cornell.edu writes: > >> >How-To-Repeat: > >> 1. vipw and append "+:::::::::" > >> 2. edit /etc/group and append "+:" > >> 3. start ypbind > >> 4. edit /etc/inetd.conf and append: > >> amanda dgram udp wait backup /usr/local/amanda/libexec/amandad amandad > >> 5. send HUP signal to inetd > >> > >> result: "No such user backup, service ignored". > > > >This is caused by the fact that the C library caches metainformation > >about the password files (e.g. whether or not to use NIS, whether or > >not it has access to the master password map, etc.) and there is > >currently no way of forcing it to clear its cache. > > > >This is really a libc bug, not an inetd bug. It is closely related to > >bin/10281. > Funny, I got a different response from As far as I can see, you're talking about something other than the problem with inetd not re-reading its conf file when -hup'ed here. To my knowledge *that* bug was fixed recently in both current and stable. However Dag-Erling is in a much better position to know these things, so absent evidence to the contrary, believe him. :) Sorry for any confusion, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message