Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-5114

hardcoded umask in com.sun.akuma/Daemon.java

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: core
    • Labels:
      None
    • Environment:
      RHEL 5.4
    • Similar Issues:

      Description

      Hello,

      When running hudson via winstone as below.

      /usr/lib/jvm/java-1.6.0/bin/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DHUDSON_HOME=/var/lib/hudson -jar /usr/lib/hudson/hudson.war --logfile=/var/log/hudson/hudson.log --daemon --httpPort=8080 --debug=9 --handlerCountMax=100 --handlerCountMaxIdle=20

      The umask of all the files created are set as 027 rather than the user who invokes the processes umask.

      For example a user with a umask of 022 runs hudson and a job and all the resulting files are set to 027.

      This is because the Daemon.java file that is part of akuma has a call to

      LIBC.umask(0027);

      Please can this be made user configurable or use the inherent umask of the running user.

      Thanks

      Steve Goodliff

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              sgoodliff sgoodliff
            • Votes:
              9 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: