On Tue, Nov 27, 2007 at 09:27:02PM +0530, ???????????? wrote: > Hello > I installed dansguardian , gave it's entry in my /etc/rc.conf > squid_enable="YES" > dansguardian_enable="YES" > > I am getting error at the boot time dansguardian couldn't connected to > parent proxy. Whereas squid starts without error. > I am running squid over port 3121 and dansguardian on port 8080. > > After logging in and giving command "dansguardian" it starts without any > error.
It sounds as though they're either starting in the wrong order, or dansguardian is starting before squid has had a chance to settle. You can check what order they're starting in by doing # rcorder /etc/rc.d* /usr/local/etc/rc.d/* and looking through the output for squid and dansguardian. Squid should appear earlier in the list. If they are starting in the correct order, try turning on squid's debugging to see why it is taking so long to start. If they're starting in the wrong order, you can either rename the control scripts as Mark suggested, or you can utilise the rcorder(8) mechanism. In the squid control script, you should have this block near the top: # PROVIDE: squid # REQUIRE: LOGIN # KEYWORD: shutdown And in the dansguardian control script, you should have this: # PROVIDE: dansguardian # REQUIRE: NETWORKING SERVERS squid # KEYWORD: shutdown > Plus in linux I have /etc/rc.local configuration file which i use to > run special commands after my linux boots, > How to do the same with FreeBSD. You can create /etc/rc.local if you want, and it will run at the right time. However, it is lightly deprecated these days in favour of /usr/local/etc/rc.d, as used by the ports. For each custom startup job you want to run at boot time, create an rcorder(8) style script in /usr/local/etc/rc.d. rcorder(8) gives you great flexibility over the start order. Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \
Description: PGP signature