-
-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DietPi-Software | Skip setting file permissions globally after each install #2641
Comments
@JJGO Nope permissions reset on user data is not expected on reboot, only when doing a Could you please paste:
|
I see, I correlated with the wrong thing then. Pretty much all my reboots were triggered from some install so it makes sense. I tested and a single reboot does not change permissions. The output is
Is there a way to tell |
Ah okay yes then this is expected. Currently there is no way to skip this, besides manually editing the script. But this would be reset on update etc. so I think currently your best way is to re-set permissions on boot. However I will turn this issue into a feature request to skip setting permissions for the whole user data dir on each dietpi-software install, but instead set them individually only for the dirs/files required for the currently installed software title. |
Another vote for this by John: https://dietpi.com/phpbb/viewtopic.php?f=11&t=5866 |
PR merged into dev: #3040 |
Every time I reboot the machine the permissions on
/mnt/dietpi_userdata/dokuwiki
are reset fromwww-data:dokuwiki
todietpi:dietpi
.I need the folder to have user
www-data
for the web server to edit files and the group to include other users such as the syncthing daemon.I could automate the permission change on startup but my question is why is this happening and if it is expected behavior.
Thank you
Required Information
cat /DietPi/dietpi/.version
echo $G_DISTRO_NAME
orcat /etc/debian_version
uname -a
echo $G_HW_MODEL_DESCRIPTION
or (EG: RPi3)5V 2.4A Official Raspberry Pi
SanDisk 32GB
The text was updated successfully, but these errors were encountered: