[Fwd: Re: small adjustment to install scripting is (i think) warranted]

[Mike Slifcak]

Andy Smith responds:
--- Begin Message ---
[EMAIL PROTECTED] wrote:
From: Alex Burger <[EMAIL PROTECTED]>
Date: 2004/06/08 Tue AM 08:40:49 EDT
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: small adjustment to install scripting is (i think) warranted
[EMAIL PROTECTED] wrote:
Hi Mike.
The only spot I see in the build script is in build.pl:
# Set SNMPCONFPATH environment variable so Perl conf.t test can locate
# the configuration files.
# See the note about environment variables in the Win32 section of
# perl/SNMP/README for details on why this is needed.
$ENV{SNMPCONFPATH}=t;$ENV{SNMPCONFPATH};
Is it really needed for the Perl tests to work?
Alex, I believe that you added those lines to quell errors
from a test that uses SNMPCONFPATH to locate an additional
configuration file.
Actually, it was because of the environment problem with Perl on Windows 
where changes made to the environment in one Perl script will not be 
seen by another Perl script.  It's in my notes above and in the README.


Maybe it should be defined by the installer script or better yet, fix 
the bug. :)

Alex

I doubt that the bug in question is related to the installer script,
since the bug pre-dates the installer script.  However, I claim no
knowledge either way, as I have not had time to investigate this further.
I am not saying it has anything to do with the installer script.  What I 
meant was to say I don't think we should need to add the persistent path 
to the SNMPCONFPATH because it is really a bug in the core Net-SNMP 
package that needs to be fixed, not a problem with our installer 
scripts.  We can add it as a work around I guess, but it would probably 
better to just have it fixed in the main code if it really is a bug. 
The difference between this and my work around above is that my work 
around is for a problem in Perl, not Net-SNMP.

I think having multiple values for SNMPCONFPATH will break snmpconf as 
it will try to create a file called 
/usr/etc/snmp/:/usr/snmp/persist/snmp.conf for example.

Alex

My call for change was premature... 
Now I understand you.

Snmpconf is in an unusual situation. I believe that it was created
before the world realized that SNMPv3 passphrases should be kept
separate from the basic configuration.
Andy, in light of this, do you think we should study the need
further ?

I think that in general there needs to be a seperate application for 
user management. I can see the need for a systems admin to be able to 
run snmpconf to configure the agent, but not necassarily create users, 
set up passphrases, etc. Security configs should be kept seperate from 
the rest of the configs IMHO.

Andy



[EMAIL PROTECTED] wrote:

Andy, Please add the PERSISTENT_DIRECTORY to SNMPCONFPATH
in the build scripting.
Thanks!
Here is why :
https://sourceforge.net/tracker/?group_id=12694&atid=112694&func=detail&aid=935658



--
--------------------------
Andy Smith, MCP
[EMAIL PROTECTED]
--------------------------

--- End Message ---