Thanks Mike! Yes I can see 192.168.0.160:8080 directly without Pound running - and when Pound is forced to start too. Without Pound running 192.168.0.161 doesn't resolve, but with Pound running I get the 'Service not available...' message whereas it should direct to 192.168.0.160:8080.
My pound.conf file (on Linux, I think this is same as pound.cfg) has no pound.sock reference but has what I assume is the equivalent on FreeBSD; /var/run/pound.pid. I think I set the logging to go to httpd-error.log a while ago. But now I'm just getting errors in /var/log/messages.log. Any logged errors are helpful right now! =) As I've written before, Pound should be setup to start at boot, but I have to force start it now, and even then it doesn't direct from 192.168.0.161:80 to 192.168.0.160:8080. Poundctl shows NO services running - just gives me instructions to use the command to enable/disable services. I imagine there is something missing that stops Pound being started at boot, and this is also stopping the services from running once I have forced Pound to start. It's hard to find stuff online re Pound + FreeBSD. I'm sorry to bother everyone here. I've looked everywhere! Please keep the ideas coming - I really do need to resolve this today. Thanks!!! ----------------------------------------------------------------------------------------------------------------------- Send big files for free. Simple steps. No registration. Visit now http://www.nawelny.com -- To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED] Please contact [EMAIL PROTECTED] for questions.
