Hi again

I just realize that we need to change back the umask after the file is
created. I'll update the patch tomorrow and send one that I know works.

// Ola

On Tue, Aug 2, 2016 at 12:13 AM, Ola Lundqvist <o...@inguza.com> wrote:

> Hi all
>
> I have prepared a preliminary patch for wheezy. I have not yet been able
> to test it fully (it is building right now). It looks like attached. You
> may need to modify it for later versions.
>
> Please comment. The principles should be ok even if I may have made some
> stupid copy+paste mistake. It worked fine in a little test program I made.
>
> Hope this helps
>
> // Ola
>
> On Mon, Aug 1, 2016 at 5:53 AM, Chris Lamb <la...@debian.org> wrote:
>
>> > 2) How do you plan to handle the "upgrade case" that is will you try to
>> > change the permission on already created history file or will you just
>> > handle the creation case?
>>
>> For redis, what I did was set and then unset the umask (for creation) and
>> chmod(2) the file afterwards to "upgrade" existing ones.
>>
>> I don't recommend a postinst approach (ie. chmod 0600 /home/*/.filename)
>> for
>> various reasons.
>>
>>
>> Regards,
>>
>> --
>>       ,''`.
>>      : :'  :     Chris Lamb
>>      `. `'`      la...@debian.org / chris-lamb.co.uk
>>        `-
>>
>
>
>
> --
>  --- Inguza Technology AB --- MSc in Information Technology ----
> /  o...@inguza.com                    Folkebogatan 26            \
> |  o...@debian.org                   654 68 KARLSTAD            |
> |  http://inguza.com/                Mobile: +46 (0)70-332 1551 |
> \  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
>  ---------------------------------------------------------------
>
>


-- 
 --- Inguza Technology AB --- MSc in Information Technology ----
/  o...@inguza.com                    Folkebogatan 26            \
|  o...@debian.org                   654 68 KARLSTAD            |
|  http://inguza.com/                Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---------------------------------------------------------------

Reply via email to