fix impermanence in combination with sysusers/userborn #223
Conversation
Mic92
force-pushed
the
userborn-support
branch
from
39ac7c7 to
4b34e65
Compare
Mic92
force-pushed
the
userborn-support
branch
3 times, most recently
from
af08f1b to
0bc0d03
Compare
Both remove user creation from the action phase to a systemd service. This is hopefully also easier to debug, since we now can look at a systemd service instead for log output.
Mic92
force-pushed
the
userborn-support
branch
3 times, most recently
from
d5f21cf to
8495848
Compare
No idea how this ever worked, but for me all directories in /persistent never have the write user/group permissions when freshly created. This now also ensures that permissions will change if the configuration changes, which is a nice side effect.
Mic92
force-pushed
the
userborn-support
branch
from
f1d0251 to
32b1094
Compare
| # synchronize perms between source and target | ||
| chown --reference="$realSource" "$target" | ||
| chmod --reference="$realSource" "$target" | ||
| chown "$user:$group" "$realSource" "$target" |
There was a problem hiding this comment.
See commit message for reasoning.
There was a problem hiding this comment.
I'm a bit skeptical of this, since it would apply mode changes to already existing directories, whether a mode is supplied for the directory or not. I'm not really sure what's not working for you, though. Are the initial directories created with the incorrect permissions?
There was a problem hiding this comment.
Also, I guess this isn't critical for the main purpose of this PR, so maybe it could be moved to its own?
|
Can be tested with In the vm do: to see that permissions and owners are correct now. |
| # synchronize perms between source and target | ||
| chown --reference="$realSource" "$target" | ||
| chmod --reference="$realSource" "$target" | ||
| chown "$user:$group" "$realSource" "$target" |
There was a problem hiding this comment.
I'm a bit skeptical of this, since it would apply mode changes to already existing directories, whether a mode is supplied for the directory or not. I'm not really sure what's not working for you, though. Are the initial directories created with the incorrect permissions?
Both remove user creation from the action phase to a systemd service. This is hopefully also easier to debug, since we now can look at a systemd service instead for log output.