Date: Mon, 15 Jan 2001 22:13:43 -0800 From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: "'Shill'" <shill@free.fr>, "'Lanny Baron'" <lnb@FreeBSDsystems.COM>, <freebsd-questions@FreeBSD.ORG> Subject: RE: inetd and identd Message-ID: <003301c07f83$7affc640$1401a8c0@tedm.placo.com> In-Reply-To: <3A63D75C.D870748C@verizon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Your really confusing my poor brain with the mixed swapping of identd and inetd that seems to be in your posts! All inetd does is spawn off other programs in response to incoming network requests. I'm really not sure how setting it up with debugging enabled is going to help. Neverthless, the reason your system hands is that according to the man pages, inetd -d runs in the foreground, not the background. When the system boots, it executes programs in the rc scripts. Every one of these startup programs must in effect "detach" from the process running the rc scripts, to allow the script processor to continue on to the next statement. This is done by starting the various programs as daemons, independent of the parent rc script that started them. When the rc scripts fires up inetd, it does so very early on in the system's boot phase, I think even before the system goes multiuser, certainly well before the console is started up. Putting a foreground program (which is what inetd -d does) in there transfers control from the shell executing the rc script to the inetd program, and the whole shebang shudders to a halt. If the inetd program were to exit, the rc script would pick up where it left off. But, it can't exit because at that time the console hasn't even been brought up, and networking isn't up, so you can neither Cntl-C it from the console, or telnet into the system and kill it. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Shill >Sent: Monday, January 15, 2001 9:09 PM >To: Lanny Baron; freebsd-questions@FreeBSD.ORG >Subject: Re: inetd and identd > > >Lanny, > >Thanks for the advice. I was planning on trying another ident >daemon. However I'm still puzzled and am still looking for answers >to my questions: > >(1) Why does inetd -d (debugging mode) hang my box? >(2) Does the inet daemon's auth -r not work at all? > >(1) is the worse. If I try to boot with the -d flag, the box hangs >at boot and I need to reset it, boot -s, fsck, and then mount / in >read/write mode just to be able to edit rc.conf... > >(2) is just annoying. Did anybody get auth to work with the -f flag? >I really want to be able to give fake ident replies but if I have >to, I'll just install a daemon from the ports. > >It's just my nature. I can't ignore the problem, I have to know why >it doesn't work :P > >> You may want to install pidentd which is in >/usr/ports/security/pidentd. >> That will get you your ident. Then next thing you may want >to try is to >> uncomment the following line in /etc/inetd.conf: >> #auth stream tcp wait root /usr/local/sbin/identd identd -w t120 > >> When that is done you need to find the pid of inetd. >> Type ps auxw | grep inetd >> You will see a number like shown below: > >Or faster still: cat /var/run/inetd.pid > >Shill > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003301c07f83$7affc640$1401a8c0>