On Wed, 2004-02-11 at 23:35, John L. Singleton wrote: > Thomas, > > Well, if you authenticate over a network, with a tool such as the > Database Instance creation wizard, you must supply your credentials. > You can't log in as DBM, or DBA, as these users do not yet exist. You > /can/ log in as either the owner of the MaxDB installation, or as a user > that belongs to the MaxDB administrators group.
[trim hash ciphers 101] Ok. I was never bitten by that because I create my instances using a combination of "ssh to the server" and "run my create_sapdb script". I think you've got a correct analysis of the problem : x_server is not pam aware and does not support md5. I see three solutions (the bad one, the hard one, and the workaround one) : - bad : reset your password with crypt - hard : hack pam support into x_server and get free beer - workaround : chroot your maxdb -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
