On Tue, Apr 10, 2007 at 08:37:36PM +0200, Enrico Weigelt wrote:
> I've now tried for hours to create new users and set and pasword,
> without any succes. The user is (probably) created with pdbtool 
> (as descripbed in the docs), but setting an password failed.
> 
> cpasswd returned with RPC2_NOBINDING(P) and au cp segfaults
> directly after asking vice name and password.

RPC2_NOBINDING would indicate that the auth2 daemon isn't running. The
au segfault could be related.

In any case when you create a new user with pdbtool, it doesn't yet
exist in the auth2 password database. You first have to 'enable' the
user with,

    au nu	(newuser)

This creates the entry in auth2.pw and from then on the password can be
changed with cpasswd or au cp. You may have to explicitly specify the
host where the read/write copy of the auth2.pw file is located (i.e. the
SCM/first server you set up). That would be something like
    'au -h scmserver nu'

> Is there any way for directly writing it to the password
> database ?

There may be, but I've always used au nu to activate new user accounts.

Adding a user with pdbtool doesn't activate the account for Coda, this
way if we ever get something like LDAP integration, you could have the
user/group information coming from a campus or company wide database,
but still control which subset of those users has permission to
authenticate with Coda.

Jan