12 Jun, 2009

1 commit


10 Jun, 2009

1 commit


05 Jun, 2009

1 commit


15 May, 2009

1 commit


06 May, 2009

3 commits

  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5324 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • The fix will improve the user experience in Windows when installing from a ZIP file.  When the JVM is installed, the java.exe is contained in the PATH environment variable.  The fix consists on trying to see if java.exe is on the PATH by calling java.exe -version if no OPENDS_JAVA_HOME nor JAVA_HOME environment variables are defined..
    
    Note that even though this is an expensive operation in term of resources, this will only be called when the setup is launched for the first time.  The setup will update the environment of execution of OpenDS and this call will no longer be made.  The exception to this is the case where the user removes all the environment by deleting the files generated by the setup (or dsjavaproperties), this is done usually when the java environment has changed and the user has been told to do so (and also told to call dsjavaproperties).  Once dsjavaproperties is called again (the normal procedure to configure the execution environment) this 'extra' call to java.exe will not be made in the scripts.
    
    In other words, the fix will only have a performance penalty when the user calls 'setup' for the first time (and no OPENDS_JAVA_HOME or JAVA_HOME env variables are defined) and when the user resets the execution environment (and so is supposed to call dsjavaproperties).  This small penalty (some extra tenths of a second) is acceptable because with the fix in most of the cases the user will not have to set OPENDS_JAVA_HOME (dealing with environment variables is a rare procedure for Windows users).  As a result of this the user experience will be much smoother than what is today.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5323 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@5320 41b1ffd8-f28e-4786-ab96-9950f0a78031
    sin
     

05 May, 2009

1 commit


04 May, 2009

1 commit


29 Apr, 2009

1 commit


16 Apr, 2009

1 commit

  • Fix ServiceTag Registration adding debug message in case of error
    Fix 2619 : ldap tools always return 1 in case of argument parsing error
    Fix 3690 : SNMP: incorrect value for dsServerDescription entry
    Fix an error in the util script when the install dir is != instance dir
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5239 41b1ffd8-f28e-4786-ab96-9950f0a78031
    fguigues
     

14 Apr, 2009

1 commit


09 Apr, 2009

2 commits

  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5209 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jcambon
     
  • The fix has three parts.
    
    1. Currently the code of ldif-diff does not take into account the syntax of the attributes.  Basically the comparison of values is a non-case sensitive String comparison.  In order to be able to take into account the syntax of the attributes a config file must be provided to LDIFDiff.  This is fixed by invoking _server_script instead of _client_script on the command-line scripts (ldif-diff and ldif-diff.bat).
    
    2. There is a problem with the normalization in the org.opends.server.schema.UserPasswordExactEqualityMatchingRule class.  Currently the normalized value in the case of an encoded password is the lower-case version of the value.  For instance:
    
    value: {SSHA}cJNE9kjr52rZmttLaIrl4bOelWfvlM3Luk4Q7g==
    normalizedValue: {ssha}cjne9kjr52rzmttlairl4boelwfvlm3luk4q7g==
    
    The fix consists on only normalizing the encoding tag:
    value: {SSHA}cJNE9kjr52rZmttLaIrl4bOelWfvlM3Luk4Q7g==
    normalizedValue: {ssha}cJNE9kjr52rZmttLaIrl4bOelWfvlM3Luk4Q7g==
    
    
    3. If we load the configuration and we always use the schema check when reading the provided LDIF files, if those files are not compatible with the schema on the installation where they are being run, the ldif-diff will not work.  In order to keep the current behavior (and thus accept LDIF files that are not compatible with the schema of the installation) a new argument has been added to the ldif-diff command-line (checkSchema).  The user must provide this argument if a strict comparison of the values must be made.  Adding this attribute allows to keep the current 'tolerant' behavior of ldif-diff, however it makes the use of the command-line a bit more complex.  I personally think that having the possibility of running ldif-diff regardless of the schema overweights the problematic added complexity, but maybe someone disagrees (or has a better alternative than adding this argument).
    
    The changes in LDIFDiff correspond to the new argument.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5208 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

01 Apr, 2009

1 commit


30 Mar, 2009

1 commit

  • A while ago, I moved the replication tasks to the replication package so that
    all the replication code stay in the replication packages and to avoid
    to make method public.
    However it now appears that this break the compatibility of the 1.3 builds
    with dsreplication fron older release.
    
    This change therefore reverts previous change, moving back the replication
    tasks to the tasks package.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5149 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

25 Mar, 2009

1 commit


23 Mar, 2009

2 commits


20 Mar, 2009

1 commit


18 Mar, 2009

2 commits


16 Mar, 2009

1 commit


15 Mar, 2009

2 commits


12 Mar, 2009

1 commit


10 Mar, 2009

1 commit


09 Mar, 2009

2 commits


25 Feb, 2009

2 commits

  • JVM settings were used by scripts when checking the validity of the instance.
    This modification removes the use of the JVM setting during the bootstrapping phase.
    This fixes the following issues:
    
       * if JVM is configured for the server instance suspends on start up
         for debugging, the server suspends during the bootstrapping phase
         rather than when the real server instance has started. (remaining
         issue related to issue 3711)
       * if the JVM is configured to use more than around 45% of the
         machine's memory, we run out of memory (issue 3798)
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5032 41b1ffd8-f28e-4786-ab96-9950f0a78031
    chebrard
     
  • we now unify _script-util.sh return code: we return 0
    (success) or 1 (error).
    
    Additional error messages have been also added in order to send
    a better feedback to the user.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5029 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     

20 Feb, 2009

1 commit


13 Feb, 2009

1 commit


10 Feb, 2009

1 commit


02 Feb, 2009

1 commit


31 Jan, 2009

1 commit


28 Jan, 2009

1 commit


26 Jan, 2009

1 commit

  • 3646 	configure script fails to retrieve the user/group of the ins
    3647 	Missing license file
    3648 	Third party license files should be merged
    3649 	Wrong copyright file in SVR4 package
    3650 	LDAP tools are missing in SVR4 package
    3651 	Server is not stopped after package removal
    3654 	SVR4 pkginfo not compliant with Solaris rules
    3658 	no man pages in SVR4 package
    3661 	SVR4 only: OpenDS fails to start with 1.1.0 bld3
    3663 	SVR4: unable to start OpenDS if user has no home directory
    3664 	SVR4: delimiter used in copyright file is not the one define
    3706 	configure: configure -H/-V doesn't work when the instance is
    3707 	unconfigure: unconfigure --wrongoption should display the us
    3708 	stop-ds: stop-ds -R doesn't work
    3729 	incorrect exit codes for configure/unconfigure scripts
    3735 	OpenDS failed to start if build number contains version qual
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@4911 41b1ffd8-f28e-4786-ab96-9950f0a78031
    chebrard
     

21 Jan, 2009

1 commit

  • Remove the status-panel scripts and also the list of scripts in the java properties panel.  The java properties panel has also been modified to display (by default) only the command-lines that are relevant for tuning of the java arguments (start server, offline import, verify index, etc.).
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@4896 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

15 Jan, 2009

1 commit