Uploaded image for project: 'SET - Setups'
  1. SET - Setups
  2. SET-187

Setup should consider the account who started the setup

    XMLWordPrintable

Details

    • Fix
    • Status: Released (View Workflow)
    • Minor
    • Resolution: Fixed
    • 1.13
    • 1.13.4
    • None

    Description

      Current Situation

      When installing the JobScheduler Master or the JOC Cockpit under linux with the user user_name, it may happen that the installed files do not belong to user_name but to the user root. The reason for this could be that the environment variable SUDO_USER is not set correct.

      Desired Behavior

      The setup should use the actual user by default even if the environment variable SUDO_USER is not set. It should be possible to start the setup.sh script with a parameter that contains the user to be used for the setup. Resolved with SET-174.

      The file /etc/default/joc belongs to root:root after a JOC setup even when setting the user.

      Maintainer Note

      • The setup tries to detemine the current user via the SUDO_USER environment variable.
      • Since Issue SET-174
        • This is only a default for that user for whom the setup should be executed.
        • If SUDO_USER is empty then "root" is the default user.
        • The user for whom the setup should be executed can be entered in
          • the <entry key="runningUser" value=""/> element of the jobscheduler_install.xml or joc_install.xml
          • a form during the setup dialog

      Attachments

        Activity

          People

            oh Oliver Haufe
            ur Uwe Risse
            Anuj Mandloi Anuj Mandloi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: