Send Motion-user mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: Can't set group write permission for directories/files
created by motion (Henk Demper)
2. Re: Can't set group write permission for directories/files
created by motion (Damian)
----------------------------------------------------------------------
Message: 1
Date: Wed, 30 Dec 2020 22:36:16 +0100
From: Henk Demper <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] Can't set group write permission for
directories/files created by motion
Message-ID:
<as8pr10mb4373b5e0fef83c99bb664e5293...@as8pr10mb4373.eurprd10.prod.outlook.com>
Content-Type: text/plain; charset=us-ascii
Hello Damian,
Yes, I see now in util.c that the mode parameter in the call to mkdir() does
not include S_IWGRP (or S_IWOTH).
With umask only masking bits out of mode, that effectively means you can indeed
never add those 2 bits anymore...
I'm not very in favour of applying a local change at each update and manual
build...
For user configuration ease, isn't the idea (standard behaviour ?) to call
mkdir with mode 777
(just as fopen() always opens files internally with mode 666)
and then have the user set umask (default/normally 022) to mask off any bits
afterwards ?
Or would there be a specific reason to never allow S_IWGRP or S_IWOTH for
directories ?
If no compelling reason, should I report this as a feature request/bug, what is
your opinion ?
Anyway, as the files do now have S_IWGRP applied (thanks again) when setting
umask 002, I can continue to move/delete (without becoming root) the video
files for automatic archiving purposes, as long as I make sure that I manually
once change (with sudo chmod g+w) each created directory from 755 to 775 and
never delete them afterwards. So that part is solved :-)
Thanks for any advise,
Henk Demper
> On 29 Dec 2020, at 18:33, Damian via Motion-user
> <[email protected]> wrote:
>
> Correction, 0755 not 0750, but that does not change things.
>> The motion-internal mycreate_path() function uses 0750.
>
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
Message: 2
Date: Wed, 30 Dec 2020 22:47:16 +0100
From: Damian <[email protected]>
To: [email protected]
Subject: Re: [Motion-user] Can't set group write permission for
directories/files created by motion
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
> For user configuration ease, isn't the idea (standard behaviour ?) to call
> mkdir with mode 777
> (just as fopen() always opens files internally with mode 666)
> and then have the user set umask (default/normally 022) to mask off any bits
> afterwards ?
> Or would there be a specific reason to never allow S_IWGRP or S_IWOTH for
> directories ?
> If no compelling reason, should I report this as a feature request/bug, what
> is your opinion ?
I would like 0777 as well.
> Anyway, as the files do now have S_IWGRP applied (thanks again) when setting
> umask 002, I can continue to move/delete (without becoming root) the video
> files for automatic archiving purposes, as long as I make sure that I
> manually once change (with sudo chmod g+w) each created directory from 755 to
> 775 and never delete them afterwards. So that part is solved
If your goal was only moving/deleting, then I didn't really help you, because
the file mode is irrelevant then.
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 174, Issue 12
********************************************
