General discussion about Chef

[chef] Re: Is CHEF-686 back from the dead? (umask problem)


Chronological Thread 
  • From: Eric-Olivier Lamey < >
  • To:
  • Subject: [chef] Re: Is CHEF-686 back from the dead? (umask problem)
  • Date: Sat, 12 Feb 2011 17:19:42 +0100
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=jyq2DKkGX7TLTmXI5Gg+TvKaTyoGP37X9STq781K28LxSin/DPrTLMIANWEjdIx5Tf pyMt0KxtfeGjVbwww8qodzghZvgigq69CfOTapdaeiB0RJ/04KVJIq+QhlEM8yiKRA10 UMy24N15lryAP6qkUTMR5vpvssfR2sArS4Q/U=
On Mon, Feb 7, 2011 at 10:48 PM, Eric-Olivier Lamey 
< >
 wrote:
>  Hi everyone,
>
>  I am seeing umask problems on a test chef install and, before
>  reopening CHEF-686, I wanted to try to understand if this comes
>  from my own mistake or if the umask setting code has been lost
>  since 0.7.16.

  Hi,

  Has anyone seen the same problem as I have? Do you have any log
  file, cache or generated certificate which are world writable permission?

  If I add
    File.umask Chef::Config[:umask]
  at the end of "config/init.rb" for chef-server-api and chef-server-webui,
  the problem is fixed.

  Thank you.

Archive powered by MHonArc 2.6.16.

§