MJBarber@Hearst.com
2005-Jan-25 16:42 UTC
[Samba] Samba file server permission/ownership - winbindd
Domain: NT4 domain controller Samba: Suse 9.2 with Samba 3.0.9 Winbind seems to be the holy grail of account management in that I do not have to create the users on every samba box just the NT4 domain controller? Right? I have an existing samba setup in which the users all had local accounts. I would like to move this to a winbindd setup and eliminate that headache. After doing some work and getting winbindd setup I notice that getent passwd shows everyone with the same group ID and sequential user ID.... These in no way shape or form match the original UID/GID values...moving the GID was not hard. However, I am guessing I need to reassign the UID to what winbind says it is? Directory and file permissions should probably be 700? Thanks, Michael J Barber WPTZ/WNNE Computer Services Administrator p 518-561-5555 f 518-561-5940 Domain: NT4 domain controller Samba: Suse 9.2 with Samba 3.0.9 Winbind seems to be the holy grail of account management in that I do not have to create the users on every samba box just the NT4 domain controller? Right? I have an existing samba setup in which the users all had local accounts. I would like to move this to a winbindd setup and eliminate that headache. After doing some work and getting winbindd setup I notice that getent passwd shows everyone with the same group ID and sequential user ID.... These in no way shape or form match the original UID/GID values...moving the GID was not hard. However, I am guessing I need to reassign the UID to what winbind says it is? Directory and file permissions should probably be 700? Thanks, Michael J Barber WPTZ/WNNE Computer Services Administrator p ?518-561-5555 f ? 518-561-5940 ========================================================This e-mail message is intended only for the personal use of the recipient(s) named above. If you are not an intended recipient, you may not review, copy or distribute this message. If you have received this communication in error, please notify the Hearst Information Services HelpDesk (helpdesk@hearst.com) immediately by e-mail and delete the original message. =========================================================