-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Lueck wrote:
| Gerald (Jerry) Carter wrote:
|
| File Access checks is done by the OS. There is no
| associated tdb for file system perms.
|
| Say Jerry, I didn't catch where you were going with that. I am
| suspecting share level access
Gerald (Jerry) Carter wrote:
File Access checks is done by the OS. There is no
associated tdb for file system perms. The only possible
option might be if you tweaked the share permissions
(via server manager) in share_info.tdb.
Nope, don't have the things set up to allow the Windows tools
Gerald (Jerry) Carter wrote:
File Access checks is done by the OS. There is no
associated tdb for file system perms.
Say Jerry, I didn't catch where you were going with that. I am suspecting share level access issues, not file level. Currently I have not gotten into ACL's and all of that
Think I found something... Jerry, seems like an old setting is leaking up
through the floor boards.
Before the net rpc rights grant domain\\account SeMachineAccountPrivilege stuff existed, I used admin users = @domadmin to get the job done. That unfortunately made accounts root on the server.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Lueck wrote:
| Think I found something... Jerry, seems like an old setting is leaking
| up through the floor boards.
|
| Before the net rpc rights grant domain\\account
| SeMachineAccountPrivilege stuff existed, I used admin users =
|
Gerald (Jerry) Carter wrote:
Nah. Remember that smbd runs as root and changes back
and forth to the uid of the user.
OK, I have been reminded.
That connection / computer / etc... has flipped back to showing special account name in lsof AND I can write to the drive at this point. This box has
Michael Lueck wrote:
But then, I AM going to upgrade the Samba version after the process gets
done, so then it is an all new ball game after that. ;-)
All right, general Spring Cleaning on my Samba configuration. Updated to the 3.0.20b Debian Sarge packages. Saw various things I was not 100%
