From nobody@FreeBSD.ORG  Mon Dec 13 04:26:26 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id CABC414D50; Mon, 13 Dec 1999 04:26:26 -0800 (PST)
Message-Id: <19991213122626.CABC414D50@hub.freebsd.org>
Date: Mon, 13 Dec 1999 04:26:26 -0800 (PST)
From: emmanuel.dupont@alcatel.fr
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: inetd makes FreeBSD crash
X-Send-Pr-Version: www-1.0

>Number:         15457
>Category:       misc
>Synopsis:       inetd makes FreeBSD crash
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Dec 13 04:30:01 PST 1999
>Closed-Date:    Mon Dec 13 07:38:06 PST 1999
>Last-Modified:  Mon Dec 13 07:43:27 PST 1999
>Originator:     emmanuel dupont
>Release:        FreeBSD 3.3-RELEASE #4
>Organization:
Alcanet International
>Environment:
FreeBSD jerry 3.3-RELEASE FreeBSD 3.3-RELEASE #4: Wed Dec  1 10:26:47 CET 1999     root@jerry:/usr/src/sys/compile/JERRY  i386

>Description:
I was testing scripts with inetd. It crash the pc.
>How-To-Repeat:
echo prox 3128/tcp >>/etc/services
echo prox stream tcp nowait/3 root /tmp/prox.sh prox.sh >> /etc/inetd.conf
cat >/tmp/prox.sh <<EOF
#!/bin/sh
/usr/bin/awk ' {print ;  print >> "/tmp/prox.log"}'
EOF
chmod 550 /tmp/prox.sh
kill -HUP `cat /var/run/inetd.pid`
telnet localhost prox


>Fix:
sorry i can't

>Release-Note:
>Audit-Trail:

From: Sheldon Hearn <sheldonh@uunet.co.za>
To: emmanuel.dupont@alcatel.fr
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: misc/15457: inetd makes FreeBSD crash 
Date: Mon, 13 Dec 1999 15:57:07 +0200

 On Mon, 13 Dec 1999 04:26:26 PST, emmanuel.dupont@alcatel.fr wrote:
 
 > I was testing scripts with inetd. It crash the pc.
 
 What does "it crash the pc" mean?  Any messages in /var/log/messages?
 Any panic message on the console?
 
 > #!/bin/sh
 > /usr/bin/awk ' {print ;  print >> "/tmp/prox.log"}'
 
 Okay, so you're effectively offering the same service as inetd's builtin
 echo service, except that you're logging what you receive to disk.
 
 Are you sure you've got enough space in /tmp?  Is /tmp and MFS?  If so,
 is its size limited, or are you giving the outside world an easy way to
 exhaust your swap?
 
 Also, I notice you're using 3.3-RELEASE.  You should be aware that a
 number of problems in inetd have been fixed in 3.3-STABLE recently.
 None of these problems cause "crash the pc" symptoms, which I've never
 seen inetd do in any case.
 
 Ciao,
 Sheldon.
 

From: emmanuel dupont <ed@jerry.netfr.alcatel.fr>
To: freebsd-gnats-submit@freebsd.org, emmanuel.dupont@alcatel.fr
Cc:  
Subject: Re: misc/15457: inetd makes FreeBSD crash
Date: Mon, 13 Dec 1999 15:10:35 +0100

 I made a mistake, the problem is not inetd. It's a null-fs one.
 I  did a "mount_null /home/tmp  /tmp"  ( my / was full ).
 I and i changed the fstab too.
 It  worked fine (seems to) but it hang with the script "/tmp/prox.sh",
 inetd is not guilty.
 Reading the "man page" i see that  null-fs was buggy so i think you
 can close this call.
 
 
 
 
 
 
 
 
 

From: Alexander Langer <alex@big.endian.de>
To: emmanuel.dupont@alcatel.fr
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: misc/15457: inetd makes FreeBSD crash
Date: Mon, 13 Dec 1999 14:14:08 +0100

 I can't reproduce this.
 
 alex:~ $ uname -a
 FreeBSD cichlids.cichlids.com 4.0-CURRENT FreeBSD 4.0-CURRENT #1: Sat
 Dec  4 18:55:47 CET 1999
 alex@cichlids.cichlids.com:/usr/src/sys/compile/cichlids  i386
 
 
 
State-Changed-From-To: open->closed 
State-Changed-By: sheldonh 
State-Changed-When: Mon Dec 13 07:38:06 PST 1999 
State-Changed-Why:  
Misdiagnosed problem.  Thanks for the quick follow-up, btw. 
>Unformatted:
