Samba utilizes the UNIX File permissions for telling Windows machines who can do what with a file. Due to this, you have a decent User and Group set of controls you can place on the files/directories that you choose to share with Samba.
Without having users in the passwd file, Samba wouldn't be able to utilize those access rights.
Yeah, it can be a paine, but it does a good job.
If having multiple user account information to track is a pain, may I suggest converting to NIS or LDAP for user authentication?
-Rob
Alexander Varga wrote:
please help me. Why I cannot create a user with smbpasswd without having this username in /etc/passwd???
###################
bash-2.05# smbpasswd -a testaccount
New SMB password:
Retype new SMB password:
Failed to initialise SAM_ACCOUNT for user testaccount. Failed to modify password entry for user testaccount bash-2.05# ############## my global in smb.conf [global] workgroup = J9_C server string = %h server (Samba %v) dns proxy = no log file = /usr/local/samba/var/log.%m passdb backend = tdbsam smbpasswd invalid users = root passwd program = /bin/passwd %u socket options = TCP_NODELAY
I compilled my samba using ./configure --prefix=/usr/local/samba --with-pam --with-pam_smbpass --with-acl-support
and made a solaris package.
-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
