From nobody@FreeBSD.ORG  Tue Jul 11 00:15:44 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 8FAE537B91E; Tue, 11 Jul 2000 00:15:44 -0700 (PDT)
Message-Id: <20000711071544.8FAE537B91E@hub.freebsd.org>
Date: Tue, 11 Jul 2000 00:15:44 -0700 (PDT)
From: scarter@pobox.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: The weirdest filesystem problem I ever saw ... It's so hard to characterize
X-Send-Pr-Version: www-1.0

>Number:         19840
>Category:       i386
>Synopsis:       The weirdest filesystem problem I ever saw ... It's so hard to characterize
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    grog
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jul 11 00:20:01 PDT 2000
>Closed-Date:    Tue Jul 11 18:56:35 PDT 2000
>Last-Modified:  Tue Jul 11 18:58:49 PDT 2000
>Originator:     Steve Carter
>Release:        3.4-RELEASE
>Organization:
None
>Environment:
[scarter@brass] uname -a
FreeBSD brass.gulp.org 3.4-RELEASE FreeBSD 3.4-RELEASE #0: Sun Jun 25 21:59:18 MST 2000     root@brass.gulp.org:/usr/src/sys/compile/BRASS-SMP  i386

>Description:

I have a pretty recent ports tree that includes mutt v1.2.  I tried to
install an updated version (v1.2.4) of mutt and started with the
usual:

[scarter@brass] tar -zxvf mutt-1.2.4i.tar.gz
[scarter@brass] cd mutt-1.2.4
[scarter@brass] ./configure 
Tunnel51281 is up, line protocol is up
configure: error: missing argument to --

I didnt even know where to start looking, so I searched my file system
for the 'Tunnel51281' string and got the following:

[root@brass] egrep -R 'Tunnel51281' /*                                       
/dev/rda0:$TEST = 'Tunnel51281 is up, line protocol is up';           
/dev/rda0:> interface Tunnel51281                                              
/dev/rda0:> Tunnel51281 is up, line protocol is down                   
/dev/rda0:> .Oct  5 11:28:56 UTC: %LINEPROTO-5-UPDOWN: Line protocol on   
Interface Tunnel51281, changed state to up                                      
/dev/rda0:> Tunnel51281            206.251.0.45    YES unset  up                
up                                                                              
/dev/rda0:! > interface Tunnel51281                                          
/dev/rda0:! > Tunnel51281 is up, line protocol is down                          
/dev/rda0:! > .Oct  5 11:28:56 UTC: %LINEPROTO-5-UPDOWN: Line protocol on      
Interface Tunnel51281, changed state to up                              
/dev/rda0:! > Tunnel51281            206.251.0.45    YES unset  up        
up                                                                             
/dev/rda0:interface Tunnel51281                                                 
/dev/rda0:interface Tunnel51281                                                 
/dev/rda0:Tunnel51281            206.251.0.252   YES unset  up      
up                                                                      
/dev/rda0:Tunnel51281 LSP: BR1.PAO-1/1 -> HR1.SNV                          
/dev/rda0:Tunnel51281

Searching further I found:

[scarter@brass] pwd
/home/scarter/bin
[scarter@brass] egrep -R 'Tunn' *
DNScheck:  $interface =~ s/Tunnel/t/;
getLSPinfo.pl:Router      Tunnel         Bandwidth   Utilization
getLSPinfo.pl:  open(ROUTER, "$command 'sh int | i ^Tunnel| BW |output rate' $router |")
getLSPinfo.pl:    $tunnelflag = 1 if $line =~ '^Tunnel';
getLSPinfo.pl:    if($line =~ '^Tunnel') {
test:$TEST = 'Tunnel51281 is up, line protocol is up';
test:print "$TEST\n" if $TEST =~ '^Tunnel';

These are scripts in my ~/bin directory

Further than this I don't even know how to describe it or fix it other
than reinstall the system, but then the problem would be gone and
you'd not be able to fix it.

>How-To-Repeat:
I can repeat it on my system as many time as needed.  But I wouldnt
know how to configure a system to do it.

I will keep the system as is for a while, I can still use it until I
need to install some software.

>Fix:

No idea ... I could delete the scripts ...

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: grog 
State-Changed-When: Tue Jul 11 00:40:19 PDT 2000 
State-Changed-Why:  
Waiting for feedback. 


Responsible-Changed-From-To: freebsd-bugs->grog 
Responsible-Changed-By: grog 
Responsible-Changed-When: Tue Jul 11 00:40:19 PDT 2000 
Responsible-Changed-Why:  
grog is responding to this PR. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=19840 
State-Changed-From-To: feedback->closed 
State-Changed-By: grog 
State-Changed-When: Tue Jul 11 18:56:35 PDT 2000 
State-Changed-Why:  
Not a bug, user error. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=19840 
>Unformatted:

Greg Lehey, 11 July 2000

Cleaned up formatting breakage.  Please break normal text lines at
round 70 characters.

It looks as if you have ~/bin in your PATH, and that bin/test is
executable.  It thus replaces test(1) in the build.  Try changing the
name of bin/test; that should solve the problems.  Please let me know
if this works.  Until then, I'm placing this PR in the 'feedback'
state.


From: Steve Carter <scarter@gblx.net> 
Date: Tue, 11 Jul 2000 11:13:53 -0700   

Heck ... and I thought I'd found a really sweet bug.  This did fix the
problem, thank you.

Closed by Greg Lehey, 12 July 2000.
