Init after everything is up?

Question

I have a service I start/stop on boot/shutdown which I'm using to help me keep track of what I'm doing while experimenting with distributions on my RPi and swapping SD cards all the time.

The problem is that I put this on my new xbian image and I only get shutdown notifications.

Everything works fine on my main Raspbian which I've customized a lot. What I'm thinking is that the base xbian doesn't do very much yet, and my Raspbian has a lot of things running now after customization like samba, so the service starts much later on my fully developed raspbian than on xbian.

So what is the correct way to ensure this script runs only once the network connection is fully up?

Here is my script:

#! /bin/sh
# /etc/init.d/boot-notify
#

### BEGIN INIT INFO
# Provides:          boot-notify
# Required-Start:    $remote_fs $syslog $network $all
# Required-Stop:     $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start daemon at boot time
# Description:       Enable service provided by daemon.
### END INIT INFO

# Some things that run always
OS=$(uname -nr)

# Carry out specific functions when asked to by the system
case "$1" in
  start)
    echo "Starting script boot-notify "
    curl -s -k \
      -F "token=token" \
      -F "user=token" \
      -F "message=Raspberry Pi ($OS) boot-notify starting" \
      https://api.pushover.net/1/messages
    ;;
  stop)
    echo "Stopping script boot-notify "
    curl -s -k \
      -F "token=token" \
      -F "user=token" \
      -F "message=Raspberry Pi ($OS) boot-notify stopping" \
      https://api.pushover.net/1/messages
    ;;
  *)
    echo "Usage: /etc/init.d/boot-notify {start|stop}"
    exit 1
    ;;
esac

exit 0

I seemed to be unable to capture the curl errors (removing -s and adding -v and >> to a log file and trying the -o option), but I added the following arguments to the startup and I'm getting boot notifications now:

  --retry 10 \
  --retry-delay 5 \
  --retry-max-time 60 \

Answer 1

If you symlink your script into the runlevel directories then you can control the order. I'm not sure what kernel xbian runs on but the runlevel directory is usually something like:

/etc/rc[1-9].d/

In this case I'll assume you're using runlevel 5, so you want to symlink your script to:

/etc/rc5.d/

The naming convention in this folder controls the order in which scripts will run and what they do.

The first character tells you if the script kills or starts a process (K or S). I'm pretty sure the order of execution is determined alphabetically, so you can control it easily for using the next two characters.

For example:

S01syslog 

Would start before:

S05network

---

I hope that helps somewhat. If I find anything else out about xbian I'll let you know.