<span class="q"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">That means something is already running on the port it's tryng to listen<br>on (Another beagled instance?) You can check with 'sudo netstat'.
</blockquote></span>
<div><br>
<br>
I've got nothing on that port according to netstat. Although, I
don't know why I didn't think of that. I guess I shouldn't stay
uo so late. :-)<br>
</div>
<span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Note that with the --debug you'll end up with a couple of GB of logs in
<br>a week :-
</blockquote></span>
<div><br>
<br>
So far that's not a probem. I can't get it to stay running more
than 10 seconds or so at a time. Right now, huge log-files aren't
a major problem.<br>
<br>
<br>
</div>
<br>
I even went in a used the beagle-config. According to that tool :<br>
<br>
Global Access to Beagle WebServices is currently DISABLED.<br>
<br>
<br>
Which is nice. So, why is it still starting it's web server?