Date: Tue, 24 Feb 1998 12:04:46 -0600 (CST) From: Kevin Day <toasty@home.dragondata.com> To: ken@plutotech.com (Kenneth D. Merry) Cc: current@FreeBSD.ORG Subject: Re: identd still not working right Message-ID: <199802241804.MAA07090@home.dragondata.com> In-Reply-To: <199802241759.KAA03340@panzer.plutotech.com> from "Kenneth D. Merry" at "Feb 24, 98 10:59:46 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> Kevin Day wrote... > > > > For me, identd is still complaining a lot. This started in early january. > > > > Feb 22 19:40:05 shell identd[23861]: getbuf: bad address (000018e8 not in f0100000-0xFFC00000) - ofile > > Feb 22 19:40:05 shell identd[23861]: getbuf: bad address (00000014 not in f0100000-0xFFC00000) - ofile > > Feb 22 19:40:05 shell last message repeated 3 times > > Feb 22 19:40:05 shell identd[23861]: k_getuid retries: 5 > > Feb 24 02:00:07 shell identd[6664]: getbuf: bad address (000042ee not in f0100000-0xFFC00000) - ofile > > Feb 24 02:00:08 shell identd[6664]: k_getuid retries: 1 > > Feb 24 08:47:29 shell /kernel: pid 17844 (identd), uid 0: exited on signal 11 > > Feb 24 08:53:15 shell /kernel: pid 18382 (identd), uid 0: exited on signal 11 > > > > I've grabbed identd again, compiled again, nothing seems to help. > > > > Anyone else seeing this? > > Make sure you kill the old identd process if it is still running. > I see those types of problems when there are VM system changes. > > Recompiling generally fixes it for me. I assume you've done a make > world to pick up all the library and header changes to go along with your > new kernel? > Yeah, it's not still the same old identd running. This has persisted throughout several make world's, and everything. I'm using the pidentd from the ports directory.... Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802241804.MAA07090>