Hi Oliver


1) Why do all those gpre lines have no -user -password arguments? They
don't work for me that way.
2) I could work around by executing the first occurrence (security.e)
manually, using those parameters.



There is global enviroment variables that you can set, it's in the
documentation.

You need it if you are not the owner of the database. (either chmod/chown or
set youself up as root user).

I think that new databases are created by the server (and have a suspicion they
are created as the ibserver user ie root or interbase).

I think the environemnt variables are

ISC_USER=SYSDBA
ISC_PASSWORD=masterkey




3) When I get to the second occurrence (array.e), gpre dumps core when
trying to process the file. Any ideas how that might come?


This happened to me heaps it's due to those nested links.

ie the file in
/tmp/build/InterBase/jrd/yachts.gdb

points to
yachts.gdb -> /tmp/build/InterBase/jrd/yachts.gdb


That was always the problem.

>
> - I need to use -user and -password for the isql command. That becomes
> a running problem in the build process. Is there a way to set that
> globally which I'm not aware of?

>
> - Why do you call that link "yachts.gdb" here? The original, which is
> created by the script, is called "yachts.lnk". Maybe that's the
> source of the problem you encounter below.

There are a lot of .lnk and .gdb files (well only about three actual names)
and links in most of the directories. Some of the gdb files were also links
after the script ran.

I only changed the one in /jrd/yachts.gdb which was a link pointing back to

yachts.gdb -> /tmp/build/InterBase/jrd/yachts.gdb

ie back to itself, There were also several .lnk's (obviously a PC person
throught of those) which also point in a similar fashon.

As long a one of the eventually points to the right spot it should work out.

>

I'll put the rest in the next version of the document.

Thanks for the tips.

Regards

Mark