ngraham added a comment.
In D21466#471371 <https://phabricator.kde.org/D21466#471371>, @bruns wrote: > In D21466#471325 <https://phabricator.kde.org/D21466#471325>, @ngraham wrote: > > > In D21466#471321 <https://phabricator.kde.org/D21466#471321>, @bruns wrote: > > > > > For group membership changes, only a relogin is required (at most). > > > > > > I know, but telling people to log out and log back in again involves more ways to mess up than just telling them to reboot. It's not really much slower or more invasive either. > > > I disagree. How could a relogin mess something up? Rebooting requires stopping everything outside the session. It may also require unlocking the harddisk, waiting for the computer to boot, repopulating caches ... Requesting to reboot may also give some bad press - "Rebooting, is this Windows??? ROFL!!!" I'm talking more about UX than technical concerns. Rebooting can be accomplished with a single button; logging out and back in requires a multi-step process that offers more ways for a user to mess it up. > > >>> The only relevant group membership here is the usershare group >> >> On Arch the group name is actually `sambashare`. I don't believe there is a consistent standard here. > > The standard is to retrieve the group from the directory. KSambaShare already fetches the directory name from the samba config (to add a watch), exposing the owner group is trivial. How can I do that? REPOSITORY R432 File Sharing (Samba) integration REVISION DETAIL https://phabricator.kde.org/D21466 To: ngraham, #vdg, #frameworks, #dolphin, apol Cc: bruns
