Bug #7034
closed
  
NTP Orphan Mode stratum setting is not displayed in input field
 
        
        Added by Thomas Rieschl almost 9 years ago.
        Updated over 8 years ago.
        
Affected Architecture:
All
 
 
  
  
  
  Description
  
  The "Orphan Mode" setting in the NTP config is not displayed in the input form field.
	It is used, though. I checked the config file (/var/etc/ntpd.conf), the correct value is used there. When submitting the form with the empty field, 12, the default value is used in the config file.
	I could reproduce it in the current stable release (2.3.2-RELEASE-p1 (amd64)), on a firewall used in production and the current nightly snapshot (2.4.0-BETA (amd64), built on Thu Dec 22 16:08:06 CST 2016), freshly installed in a VM. I don't know if non-amd64 architectures are also affected.
   
 
 
  
  
    
    
    
    
       - Status changed from New to Confirmed
 
       - Assignee set to Jim Pingle
 
       - Target version set to 2.4.0
 
       - Affected Architecture All added
 
       - Affected Architecture deleted (
) 
    
    
     
   
  
  
    
    
    
    
       - Status changed from Confirmed to Feedback
 
       - % Done changed from 0 to 100
 
    
    
     
   
  
  
    
    
    
    Wow, that was fast :)
Thanks, and happy holidays!
 
     
   
  
  
    
    
    
    I just tested it with the current nightly (2.4.0-BETA (amd64) built on Wed Jan 04 13:38:53 CST 2017; FreeBSD 11.0-RELEASE-p5). In general it works as expected, although, due to a typo, I noticed that the input is not being validated or filtered.
I could enter a non-numeric value which was accepted, but after restarting the ntpd the following error was logged:
	syntax error in /var/etc/ntpd.conf line 7, column 7
line 7 column 7 syntax error, unexpected T_String, expecting T_Integer
	Also, whitespace before and after the number is not removed, but that is just cosmetic and doesn't trigger an error.
	Thanks!
 
     
   
  
  
    
    
    
    
       - Status changed from Feedback to Confirmed
 
    
    Yep, something isn't quite right with how it's doing validation.
 
     
   
  
  
    
    
    
    
       - Status changed from Confirmed to Feedback
 
    
    
     
   
  
  
  
  
    
    
    
    
       - Status changed from Feedback to Resolved
 
    
    
     
   
  
  
    
    
    
    
       - Target version changed from 2.4.0 to 2.3.3
 
    
    
     
   
  
 
  
  
  
 
Also available in:  Atom
  PDF