Typically, you use the distribution's startup mechanisms to signify what services are required. For example, in OpenSUSE, you would define the startup script using comment meta-data that indicates what services your service is dependent upon.

Here's an example from OpenSUSE 12.3's Apache Startup Script:

### BEGIN INIT INFO
# Provides:                     apache apache2 httpd
# Required-Start:               $local_fs $remote_fs $network
# Should-Start: $named $time postgresql sendmail mysql ypclient dhcp radiusd # Should-Stop: $named $time postgresql sendmail mysql ypclient dhcp radiusd
# Required-Stop:                $local_fs $remote_fs $network
# Default-Start:                3 5
# Default-Stop:                 0 1 2 6
# X-Interactive:                true
# Short-Description:            Apache 2.2 HTTP Server
# Description:                  Start the Apache HTTP daemon
### END INIT INFO

The exact mechanism is going to depend on your distribution. You need to research your distribution and find out how this is done for your distribution.


On 8/14/13 9:34 AM, Rong Qu wrote:
How can I make sure derby is started after the network interface comes up? I am not very familiar with it, can you explain more?

I tested on a different machine yesterday, and derby was started automatically after reboot, so seems the issue was caused by machine/network configuration. Any thoughts?

Thanks!

------------------------------------------------------------------------
Date: Mon, 12 Aug 2013 17:13:58 -0600
From: [email protected]
To: [email protected]
Subject: Re: derby network server can not be started automatically

Start derby after the network interface comes up?

On 8/12/13 4:35 PM, Rong Qu wrote:

    On Linux, we wrote a script to call NetworkServerControl so that
    derby network server can be started automatically after reboot.

    After reboot, we got following error message from derby
        Can not listen on port **** on host ******
        java.net.BindException
                  Can not assign requested address

    However, using exactly same script, derby network server can be
    started manually right after the machine is rebooted.

    Any suggestions how to fix this?

    Thanks,
    Rong



--
George Sexton
MH Software, Inc.
303 438-9585
http://www.mhsoftware.com/

--
George Sexton
MH Software, Inc.
303 438-9585
http://www.mhsoftware.com/

Reply via email to