Hello Chris, On Mon, Apr 16, 2007 at 07:11:18PM +0100, Chris Cowsley wrote: > > My apache front end leaves scripts for root cron to run. > This is a tried and tested strategy (over several years). > > When root cron runs: > > /usr/sbin/useradd -d /home/uname -g staff -p 7QmZL4 uname > chfn -f "full name" uname > --- snip housekeeping in netlogon --- > /usr/bin/smbpasswd -x uname > wait > (echo spaswd ; echo spaswd)|/usr/bin/smbpasswd -a -s uname > wait > --- snip housekeeping in /home/uname --- > > I expect everything to work for me. group staff already exists. > > On my 'new' Etch (Was rc now updated) when I look in gnome user manager uname > has been created correctly with Main_group staff, but staff group does not > contain uname.
This behavior is the expected one. useradd in Sarge did not neither add the user to the group. It is not needed since this group will be the primary group of the new user. Maybe that could be a behavior change in smbpasswd, or in a PAM module, which would expect the user to be in the list of users of a group. Can you describe the problem which appears after you added the user? Is there a problem with smbpasswd afterwards? Does it output anything? What makes you think there is a bug anywhere? Kind Regards, -- Nekral -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
