Hi Reuben - thank you for reporting this bug and making Ubuntu better!

You are right: Upstart does reset the umask to 022 in a jobs environment
unless the umask stanza has been specified in a job. This is correct
behaviour for Upstart running as PID 1 but when running as a Session
Init it really should inherit the current umask and use that for all
jobs by default.

For consistency and backwards compatibility, we should also add a '--no-
inherit-umask' option.


** Changed in: upstart (Ubuntu)
       Status: New => Confirmed

** Changed in: upstart (Ubuntu)
     Assignee: (unassigned) => James Hunt (jamesodhunt)

** Also affects: upstart
   Importance: Undecided
       Status: New

** Changed in: upstart
     Assignee: (unassigned) => James Hunt (jamesodhunt)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240686

Title:
  Upstart overrides the user's umask

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1240686/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to