Thank you for looking into this! On 2012-Nov-11 16:22 (+0000), Clint Adams wrote with possible deletions: > That might surprise anyone relying on the current behavior.
Yes, I'm aware of that. On the other hand: The current behavior seems insane to me, unless there would be a good reason for by default changing the umask to a less secure setting, but then that should be documented. I agree with your objection though. To avoid that kind of trouble, I'd suggest a stepwise change: * For the next release, make run-parts issue a warning that it changes the umask, and that this behavior is going to change in the future. Suppress the warning if the user sets the umask with -u. * For the following release, change run-parts to not tamper with the umask anymore, and warn about the new situation, unless -u is given. * Finally remove the warning. Would that be of any use? Stefan -- Stefan Klinger o/klettern /\/ bis zum send plaintext only - max size 32kB - no spam \ Abfallen http://stefan-klinger.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org