New answers tagged

2

I've dug deeper into it. It seems like a wrong display of CPU usage. Reading with samba from unecrypted drive giving 112 MB/s requiring about 38 % CPU usage on whole system CPU usage is floating between 29 % and even sometimes goes shortly up to 94 % while reading from unencrypted drive. Now taking encrypting read performance of 110 MB/s reduced by 38 % ...


0

What version of samba do you have installed? Query via rpm -qa | grep samba Make sure you have samba4 installed. I am assuming the issue is related to version of SMB protocol the client is trying to use when connecting. SMB Version 1 is now disabled by default on Windows Server 2019. I would not recommend enabling it. This is an example on adding debugging. ...


0

File ACL control access to files inside a share. They apply always, regardless of which share was used to access the file (you can set up shares so you can access same file via different path); if POSIX ACL mapping is uses as the VFS method these ACL will apply even for local users (i.e. even when accessing files without Samba). Access to the share itself is ...


0

You need to set directory and file modes and/or access control list (ACL) entries so that the members of the group in question have rights to write (modify, delete) directories and/or files. You need at least to chmod g+w <directory> for group members to be able to remove files from that dir. See also what umask does, e.g. try umask 02 before creating ...


0

Why go with complicated stuff when rsync already has a command line option for this? From the man page: --atimes, -U preserve access (use) times


1

... apply sticky bit on samba share directory ... client is not able to remove files and directories created by root ... The sticky bit on a directory only allows the owner of a file to delete that file. If the root account is creating files in that directory, then only root can delete them. This is exactly what the sticky bit is designed to do. ... many ...


Top 50 recent answers are included