[GRASS-user] Database login hassles

GRASS GRASS user
1

All,

One of my Grass users is running into a consistent problem with a Mysql database login.

After running db.connect and db.login from a mapset, some maps (stored in other mapsets) retain blank usernames. Opening the other mapsets and running the db.connect / db.login does not fix the problem - in other words, for some reason Grass is failing to store the new login details.

At the moment, I just want to know the file location for the login details, so I can run a hard-code fix!

Richard Chirgwin

2

Hi,

It's a hidden file in the user account called .grasslogin6

Frank

Am Mittwoch, 28. November 2007 01:24:36 schrieb Richard Chirgwin:

All,

One of my Grass users is running into a consistent problem with a Mysql
database login.

After running db.connect and db.login from a mapset, some maps (stored
in other mapsets) retain blank usernames. Opening the other mapsets and
running the db.connect / db.login does not fix the problem - in other
words, for some reason Grass is failing to store the new login details.

At the moment, I just want to know the file location for the login
details, so I can run a hard-code fix!

Richard Chirgwin
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

3

Frank Broniewski-3 wrote:

Hi,

It's a hidden file in the user account called .grasslogin6

Frank

I have expanded the module documentation of db.login accordingly.

Markus

--
View this message in context: http://www.nabble.com/Database-login-hassles-tf4885474.html#a14027318
Sent from the Grass - Users mailing list archive at Nabble.com.