I can certainly see /opt/java/db/bin getting added, but what would an init script include? can you give me an example, or better yet, a file :)

Getting added? Who added it? In Arch package or in upstream?

An init script would start, restart, stop the JavaDB without having another software that manages it. Some application servers such as Glassfish are able to do it afaik but a standalone option would be nice.

I'll see if I can create an init script and let you know.

Can you please answer my first 3 questions?

When I said I can see it getting added, I agreed that it should be put into the profile file.
I haven't included it yet because I'm still waiting for the init script.
That probably answers all 3 questions.

Added the db/bin to the profile in pkgrel 3, now only awaiting your init script.

Hi Thomas,

I've just created the necessary files for an init script. There are 2 files:

1) derby-network-server.conf -> /etc/conf.d/derby-network-server (stores the setting for logging to /var/log/derby.log)
2) derby-network-server -> /etc/rc.d/derby-network-server (init script)

Any comments are welcomed! :)

I tried running your script, and all seems fine (I have nothing to test it against) but the only thing that I have noticed is that there is a derby.log file in the current directory from which I ran "sudo /etc/rc.d/derby-network-server start" which was not expected because it should have been located in /var/log/derby.log and no file was located at /var/log/derby.log

Hello Thomas,

As I've mentioned in my earlier post, you should place derby-network-server.conf into /etc/conf.d with the name derby-network-server

When the init script finds that file, it will place the log file into /var/log/derby.log

Btw, you can verify that the derby network server is working by looking at the listening ports:

$ sudo netstat -tapn

You should see java listening to 1527.. If that's the case, derby is working for you :) You can also see it under running daemons and in the output of ps aux

I've tested the script against unnecessary starts and stops despite the server is running or has stopped, so you also test it for yourself.

Thanks!

Another thing to know. I've renamed the script and configuration files to derby-network-server because derby can also run as an embedded server which you just do it by providing the jar to your project and that you don't need to have an init script for. To clarify what these files do, I just renamed them that way..

ok, my problem was that I was installing the .conf to /conf.d not /etc/conf.d
everything seems to be working, so I will include this shortly in pkgver 4