Hi Mark,

> Well I'm absolutely sure that I did not add username/password to the command line, nor defined ISC_USER/ISC_PASSWORD environment variables. All I typed was:
>
> gbak -Z mydb-prod mydb.fdb

This is what you said in your original posting. When I tested that what
the new docs said was correct, I tried this exact command (ok, different
database alias and backup file!) as root, as firebird and so on. Each
time I ran the gbak, I was prompted to enter my username and password.

I'm a tad confused! What login are you running the commands under?

> mydb-prod is an alias to /opt/firebird/mydb.fdb, and my current directory is /opt/firebird. This command started to generate a backup on top of the database, erased the database, and failed the backup in absence of a database.
>
> Note that when I run
>
> gbak mydb-prod /opt/dump/mydb.fbk
>
> I also get a backup (the proper way). So I guess my configuration does not need a user/password?

You don't and any rogue environment variable lying around do you? "env |
grep -i i[s]c" should show them up if so. Otherwise I can't figure out
why you don't get asked for a password.

Oh, this assumes Linux of course, which is what I did my testing on.

> Thank you for updating the gbak documentation. I'm pretty sure I would not try the gbak -Z anymore to get a version ID if I had read the newly added warning.

Sorry you had the trouble!


Cheers,
Norman.

--
Norman Dunbar
Dunbar IT Consultants Ltd

Registered address:
Thorpe House
61 Richardshaw Lane
Pudsey
West Yorkshire
United Kingdom
LS28 7EL

Company Number: 05132767