# DVR umask

**URL:** <https://forums.plex.tv/t/dvr-umask/841684>\
**Category:** Live TV & DVR\
**Tags:** server-linux\
**Created:** [May 20, 2023, 1:08pm UTC](https://forums.plex.tv/t/dvr-umask/841684 "2023-05-20T13:08:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![UKenGB](https://avatars.discourse-cdn.com/v4/letter/u/bcef8e/32.png) [@UKenGB](https://forums.plex.tv/u/UKenGB)\
**Post date:** [May 20, 2023, 1:08pm UTC](https://forums.plex.tv/t/dvr-umask/841684/1 "2023-05-20T13:08:28Z")

</div>

PMS running on OpenMediaVault, i.e. debian, Linux 6.1.0-0.deb11.6-amd64

When ‘recording’ from a tuner, PMS is creating files and folders without write permissions for group. However I need group write permissions for another actual user in the same group to be able to sometimes manipulate the files that PMS has created. I don’t really want to change the default umask for all users, so…

How can I set the plex user’s umask to 002 instead of 022?

So far I just chmod what PMS has created to add group write permissions, but I don’t want to have to keep doing this. I want to configure PMS to do what is required in the first place.

---

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [May 22, 2023, 1:43am UTC](https://forums.plex.tv/t/dvr-umask/841684/2 "2023-05-22T01:43:09Z")

</div>

> [@Linux Tips](https://forums.plex.tv/t/linux-tips/276247/3):
>
> Customizing your Plex configuration on systemd based systems This information is intended for those systems where cat /proc/1/comm returns systemd. On systems which use Systemd (Ubuntu 16+, Fedora, Centos 7, Debian 8,) you create this customization file which SystemD reads prior to launching PMS. This file is independent of the default configuration and service control mechanisms in /lib/systemd/system/plexmediaserver.service. Your customization override is preserved across updates, uninstal…

---

<div class="post-metadata">

**Author:** ![UKenGB](https://avatars.discourse-cdn.com/v4/letter/u/bcef8e/32.png) [@UKenGB](https://forums.plex.tv/u/UKenGB)\
**Post date:** [May 22, 2023, 9:49am UTC](https://forums.plex.tv/t/dvr-umask/841684/3 "2023-05-22T09:49:42Z")

</div>

Thanks @ChuckPa, however those instructions indicate 4 possible settings:-

UMask=002  
Umask=002  
UMask=0002  
Umask=0002

With a warning that it’s important to get it right (I’m guessing otherwise it simply won’t work), but no indication of which is correct, nor how to find out.

I suspect this should work:-

UMask=0002

Can you confirm that for a debian based system?

---

<div class="post-metadata">

**Author:** ![UKenGB](https://avatars.discourse-cdn.com/v4/letter/u/bcef8e/32.png) [@UKenGB](https://forums.plex.tv/u/UKenGB)\
**Post date:** [May 22, 2023, 9:57am UTC](https://forums.plex.tv/t/dvr-umask/841684/4 "2023-05-22T09:57:08Z")

</div>

Ignore that question.

‘_systemctl show plexmediaserver_’ includes UMask=0022, so that will be the correct format.

All sorted. Thanks again.

---

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [May 22, 2023, 10:22am UTC](https://forums.plex.tv/t/dvr-umask/841684/5 "2023-05-22T10:22:57Z")

</div>

@UKenGB

Those instructions support all variants of Linux Plex supports; inclusive of the NAS Linux systems.

That’s why the warning exists 🙂

The installer does a lot for users but there are some things it can’t possibly know nor safely assume. Sometimes RTFM is your friend 🙂

( This is Linux, not Windows 🤣 )

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [August 20, 2023, 10:23am UTC](https://forums.plex.tv/t/dvr-umask/841684/6 "2023-08-20T10:23:46Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
