How can I force the passwd command to use MD5 hash and not to use crypt? I need to get the passwd command to talk to the ldap server (which it does) and use MD5 when I change passwords for the users.
It seems that I have missed out on something fundamental on how I can mount a home smb-share on a linux client used by many users. This isn't a problem with NFS - I have mounted /home/users/ on all clients, so that /home/users/user-a and /home/users/user-b will find their homedir then they log on. But how do I do this with SMB? I should mount /home/users in fstab - because I'll have to mount this SMB-share with a defined users rights, and that won't work as several users dir where they find their homedir.
AutoFS? A login script when the user log on? Isn't this automated in any of the linux distros? What have I missed out on?
I have the 389 Directory Server, 800 users and two file servers for the homedirs (active users...) and I use NFS - but I'm thinking about using SMB instead of NFS, but I really don't know how to mount the homedir for each user.
I need a way (a script) too move all but the last 100 messages from a users mail-spool (/var/spool/mail/theuser) to a file/mbox in the users mail-directory (/home/theuser/mail). Is there an easy way to do this?
If I mount a samba share like this from a linux server using ACL in ext3...
mount -t cifs //192.168.0.10/smbshare /mnt/smbshare -o user=root password=secret
...and access the share with linux/smb-user smbuser. I have given smbuser write access to all catalogs, but when I write something to the share the owner becomes root (the user that mountet the share).
Is there any possibility to make smbuser the owner of the files/catalogs he creates even if the share is mountet by the root-user?
This case is supposed to work on a linux terminal server so many different users access the smb share (mountet by root).