Skip to content
Snippets Groups Projects
Commit f82e55f6 authored by Robert Martin-Legene's avatar Robert Martin-Legene
Browse files

Fixed documentation to call the correct script from crontab on reboot. Also changed cron.sh a bit.

parent 4c8d5924
No related branches found
No related tags found
No related merge requests found
...@@ -9,7 +9,7 @@ ...@@ -9,7 +9,7 @@
4. `source ${HOME}/bfa/bin` 4. `source ${HOME}/bfa/bin`
- You can include this line in your .bash_profile if you want. - You can include this line in your .bash_profile if you want.
- It is perfectly safe to source it multiple times. - It is perfectly safe to source it multiple times.
5. Install this crontab: `@reboot bfa/network5445/start.sh` 5. Install this crontab: `@reboot bfa/bin/cron.sh`
- If you are running a sealer you MUST do this. - If you are running a sealer you MUST do this.
6. run `start.sh`. This will start synchronizing and probably takes at least an hour. 6. run `start.sh`. This will start synchronizing and probably takes at least an hour.
7. Change your node's settings with `syncmode.sh` 7. Change your node's settings with `syncmode.sh`
......
#!/bin/bash #!/bin/bash
trap 'exit 1' ERR trap 'exit 1' ERR
# Go $HOME
cd
# Log in home directory
exec < /dev/null > bfa-cron-output.log 2>&1
# Go to script bin, 'cause we expect to find $BFAHOME/bin/env there
cd `dirname $0` cd `dirname $0`
source ./env source ./env
exec < /dev/null > /dev/null 2> /dev/null
( (
./start.sh & ./start.sh &
while ./monitor.sh || true # Yes, we wait 60 seconds after starting the server.
# If you don't want to wait, kill the sleep.. the || true
# will capture the ERR trap.
while sleep 60 || true
do do
sleep 60 ./monitor.sh
done & done &
) )
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment