have to set "oplocks = false" for Word

Jeremy Allison jallison at whistle.com
Mon Apr 20 19:10:27 GMT 1998

Gerald Carter wrote:
> [root at nowhere /etc]30$ ./smbpasswd -a -m testmachine
> ./smbpasswd: User "testmachine$" was not found in system password file.
> This worked about two weeks ago I know because I am still using the
> binary compiled from then.  Is this new expected behavior?  I know there
> was talk of machine account in /etc/passwd but I never thought anything
> happened with it yet.

Yes it is intended behaviour - this is something I added
into the main branch. It seemed to me that ensuring a
machine account had a corresponding entry in /etc/passwd
was a good idea - to ensure that all machine account
entries are unique, not only within smbpasswd, but within
the UNIX password system also. This may be important at
a future date, and didn't seem a particularly onerous
requirement. I'm trying to tidy up the smbpasswd interfaces
somewhat to allow people to add different backend (ldap,gdbm
etc.) databases that scale better than the flat file we
have now.

Note that the docs/usage lag somewhat behind the implementation.
This will be the case for a while until we start getting
much closer to a real release.



Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.

More information about the samba-ntdom mailing list