Uploaded image for project: 'OODT (Retired)'
  1. OODT (Retired)
  2. OODT-672

OODT Start script does not notify user of status

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.7
    • radix
    • None
    • XDATA

    • Don't Know (Unsure) - The default level

    Description

      When starting OODT, regardless of failure or success – the output to the user is the same. Propose improvement to notify user of the status of each component.

      Current sample output:
      [asumarli@md-jl38hv1 oodt]$ ./bin/oodt start
      Using OODT_BASE: /home/asumarli/Desktop/oodt
      Using OODT_HOME: /home/asumarli/Desktop/oodt
      Using OODT_TMPDIR: /home/asumarli/Desktop/oodt/temp
      Using JRE_HOME: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.19.x86_64
      Using CLASSPATH:

      Proposed output:
      [asumarli@md-jl38hv1 oodt]$ ./bin/oodt start
      Using OODT_BASE: /home/asumarli/Desktop/oodt
      Using OODT_HOME: /home/asumarli/Desktop/oodt
      Using OODT_TMPDIR: /home/asumarli/Desktop/oodt/temp
      Using JRE_HOME: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.19.x86_64
      Using CLASSPATH:
      OODT FileManager started successfully with process id ####.
      OODT ResourceManager started successfully with process id ####.
      OODT WorkflowManager started successfully with process id ####.

      Attachments

        1. OODT-672.arni.sumarlidason.patchv2.txt
          3 kB
          Chris A. Mattmann

        Activity

          People

            chrismattmann Chris A. Mattmann
            sumarlidason Arni Sumarlidason
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment