At 04:49 PM 10/09/2004 +0300, you wrote:

> >Do you mean the user has to write files to /opt/firebird at filesystem
> >level? If so, made the (system) user a member of the firebird group. But
> >it's not desirable to allow users to write to the server's area...
> >
> >./heLen
> >
> >
> >
> >
> >
>I am sorry Helen, I did not make myself clear.
>
>For windows I can create an installer that can be deployed to any folder
>the user have write access And it must contains only 3 dlls from ebedded
>server (fbembedded.dll, jaybird.dll and msvcrt.dll). And everything
>works fine
>For linux obviously I must install classic server portion to
>/opt/firebid/ and use libfbembedded.so to call it. The problem is that
>ordinary users cannot write to /opt/firebird/. Simply I am trying to
>create an installation procedure that works for normal user and does
>not need any root privileges ... and does not need classic server
>installed on the end-user machine. That was one of the reasons I
>selected embedded firebird for my development.

"Classic server" is very light for a single user. You do need to install
fb_inet_server and its various pieces but it doesn't run unless a user
connects to it. The xinet daemon listens for a connection request and
starts a single instance of the server for each connection request.

Possibly a good place for you to start would be to look at the installation
notes for Classic, dissect the tar.gz kit, and understand what each of the
bash scripts does.

As for permissions needed to install the Jaybird pieces, you should ask on
the firebird-java list about this. It's probably in the FAQ,
anyway. Finally, write your own installer script to suit the needs of your
users.

./helen