Documentation > FAQ

1. arand is crashing mysteriously or otherwise not doing what it is supposed to do. How can I figure out what is going on so I can fix it?
   
   The best thing to do is reconfigure arand to enable debugging messages and then rebuild the binary. You can do this by passing the "--enable-debug" option to configure. Then run arand (not as a daemon) and you'll see lots of messages that indicate what is going on in the code. Most of the messages display which function they are being called from.
   
   
2. How can I run arand without running it as a daemon?
   
   Check out the full path given to the ARAND variable in the arand-run.sh script. If it says something like ARAND=/usr/local/bin/arand -d, then aran will run as a daemon. If the "-d" is not there, arand WILL NOT run as a daemon.
   
   
3. Why do I have to run arand with the arand-run.sh script? Why can't I just run arand directly?
   
   The arand.sh script deletes the default network route that is automatically added in most linux distributions when you bring up the network interface you plan to run arand on. This default route does not make any sense in ad-hoc networking since you are interested in routes to individual nodes, not to networks.