[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

9520.0. "/etc/snmpd.conf in /tmp" by BARNA::DSMAIL () Wed Apr 16 1997 10:44

    	Hi people:
    
    	I have a problem with a customer using snmp.
    	He tries to configure a default agent.
    	He uses snmp_request hostname community get 1.3.6.1.2.1.1.4.0
        command and he gets the value sysContact in /etc/snmpd.conf.
    	The problem resides when he uses the command :
      
        snmp_request hostname comunity set 1.3.6.1.2.1.1.4.0 -D
        "newcontact"
      
        The file /etc/snmpd.conf is not modified but he gets the
        new value.The file modified resides in /tmp.
        If he reboots the daemon snmpd ,it uses the values in 
        /etc/snmpd.conf (values not modified).
    
    	I have checked permisions,etc.
    	
    	Is there any debugger for snmpd?
    
    	Thanks in advanced
    
    
    	Comellas
        
    	
    
        
T.RTitleUserPersonal
Name
DateLines
9520.1SMURF::DANIELEWed Apr 16 1997 15:421
What version?
9520.24.0bBARNA::DSMAILThu Apr 17 1997 03:408
    
    	Hi:
    
    	Operating system version is Digital Unix 4.0b
    
    	Thanks
    
    	Comellas
9520.3SMURF::DANIELEThu Apr 17 1997 10:1015
The behavior should be as you expect, that the file gets
updated so the Set operation is persistent. 

It appears that the os_mibs daemon cannot rename the temp
file to /etc/snmpd.conf due to something unique to your
environment.  

The code there doesn't log error conditions though, which is
something I'll fix.

Can you try the rename manually or otherwise poke around?
How were snmpd and os_mibs started?  
What's ps say about them?

Mike
9520.4/tmp linkedBARNA::DSMAILTue Apr 22 1997 04:4919
    
    	Hi Mike:
    
    	I have looking for the reason of the problem.
    	The reason is that the customer has /tmp linked
        another partition (softlink or mount partition
        /tmp in /etc/fstab)
        Permisions are 1777 /tmp.
    	If tmp resides in root ,works ok.
    	Other aplications that uses /tmp (with tmp linked)
        works ok. 
        Can be a snmpd bug?
    
        thanks
    
    
    	Comellas