At 1:09 PM -0500 5/23/00, Andy Sinesio wrote:
>Well, I'm running NetBSD 1.4, and the identd that is supplied simply responds
>with "121" to every request.  I think pidentd is RFC1413 compliant but it
>seems this version isn't working properly.

Hmmm.  I saw a way to use telnet to test it and it did the right 
thing for me, whenever that was.  (That was pidentd on Solaris, come 
to think of it.  The NetBSD version is, or was, based on pidentd 
though.)  There are options that might make a difference.  I assume 
you have RTFM'ed.

>Do you (or anyone) know of a place I could locate a fresh m68k-compiled
>identd?  Maybe someone could gzip theirs and send it?  Or do you know which
>netbsd installation file has the identd binary so I can extract it manually
>from the tar.gz (I searched through them and couldn't find it myself).

Don't know offhand, but I can say that the NetBSD web site includes 
all the source expanded somewhere and you could go poking there for 
information if you can't find it in the tar files.

Usually if there is an installation problem with something like this 
there is more affected than just one obscure daemon.

>"Henry B. Hotz" wrote:
>
> > At 11:36 AM -0500 5/23/00, Andy Sinesio wrote:
> > >I'm currently beating my head repeatedly against a wall trying to get an
> > >RFC1413-compliant identd server to run under netbsd-mac68k. I've only
> >
> > Does the one included with NetBSD not comply with that RFC?
> >


Signature failed Preliminary Design Review.
Feasibility of a new signature is currently being evaluated.
h.b.hotz@jpl.nasa.gov, or hbhotz@oxy.edu