> In addition I think there has been more devinfo members testing and
> reporting success with these samba rpms then any other devinfo project to
> date.
That's what I thought.  I completely went into this thinking that I had
something goofy on my end.  I stripped every reminate of Samba off my test
machine and reinstalled the rpms and your fragments.  Still no go...   Whats
funny is that the deeper that I got into the problem, the more I convinced
myself that the machine script was the problem.    The Samba logs kept
pointing back to the portion of the add user script parameter that
referenced the dmc-machine-account-create script.

You know, something strange that I found when I asked the devinfo person to
send me his smb.conf was that he had two entries for the add user script.
One that used the "e-smith" approach and a second that used the traditional
samba approach (add user script = /usr/bin/adduser ......).  Could you check
your smb.conf file to verify that you have only one add user script entry?

Incidentially, this brings up another issue that I discovered with the Samba
fragments RPM.  I think when Mitel builds the blade, they need to incorprate
a script that cleans out the templates-custom dir tree for smb.conf,
otherwise rogue fragments from an old install may creep in.  This is
especially true if you had an install like mine where I had went in and made
up my own fragments.  ;)

I could be completely out in left field on this... Wouldn't be the first
time...

Thanks for having a look at this.

Best regards,

Greg





--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org

Reply via email to