Quote:
|
Originally Posted by billymayday
That's not the point. If it's SELinux that's stopping Samba running properly, you can then disable SELinux for the smb daemon alone
Try disabling with setenforce 0, then renable with setenforce 1
|
For me, it is easier to create new policies to allow smb to access what I want it to rahter than opening smb freely.
Keith
