Bug 19840

Summary: The weirdest filesystem problem I ever saw ... It's so hard to characterize
Product: Base System Reporter: scarter <scarter>
Component: i386Assignee: Greg Lehey <grog>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 3.4-RELEASE   
Hardware: Any   
OS: Any   

Description scarter 2000-07-11 08:20:01 UTC
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.

Fix: 

No idea ... I could delete the scripts ...
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.
Comment 1 Greg Lehey freebsd_committer freebsd_triage 2000-07-11 08:40:19 UTC
State Changed
From-To: open->feedback

Waiting for feedback. 


Comment 2 Greg Lehey freebsd_committer freebsd_triage 2000-07-11 08:40:19 UTC
Responsible Changed
From-To: freebsd-bugs->grog

grog is responding to this PR.
Comment 3 Greg Lehey freebsd_committer freebsd_triage 2000-07-12 02:56:35 UTC
State Changed
From-To: feedback->closed

Not a bug, user error.