tvxyvbt5

would be cool if the plugin would add a cli command to trash files

your hyperlink to mcp integration is dead

The CA description should mention that it also has an MCP server and what benefits REST has for ai-agents, because when setting up my agent, i was only searching for "mcp" in CA, got dissappointed and then went to google...

I never touched it. Just this: #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end About one month ago I configured a LAN to LAN remote share with my friend. That is mounted in here -> /tmp/unassigned.devices/smb-settings.conf: include = /etc/samba/unassigned-shares/10.253.0.2_backupsam.conf

Not fixed! I just copied a bunch of files around and the "no permission" popup came again – while copying. 😑 I copied files into an already existing `777 nobody:users` directory. But during the copying process(?) somhow the 777 became a 770. So I understand why the popup came. But why do the permissons change?? Is the solution just to run `chown -R myuser:users /mnt/user/myprivateshare`? If yes, what if I'd like to give other users acces too later?

Okay, I'm confused. How are permissions supposed to look like in a private vs a public share? I ran the "New Permissions" tool in hope it would fix those "no permissions" popups from Windows Explorer. – It did, but after creating new files/folders the issue came back. The tool set all shares to "777 nobody:users" but when I add new files/folders the permissions look like this: private share: 770 sam:users public share: 777 sam:users But is this correct? I thought this caused those permission popups in Windows Explorer. But now I can't reproduce them anymore. And I don't even know how I fixed it. (I did some restarts and updated from 6.9 to 6.10)

Private Shares get wrong permissions and wrong owner. Public shares only get wrong owner. (my username instead of "nobody")

Looks like I have the exact same problem. Everything was working but yesterday this problem occurred. I also tried two different Windows PCs and they all have the same issue so It has to be a Server problem?