Re: squid-2.5.4_6 warning: port must be 1024
On Sat, Jan 17, 2004 at 12:04:38AM -0500, Adam McLaurin wrote: Also, keep in mind you'll need to append your rc.conf with: squid_enable=YES It does seem strange that a port's behaviour would be controlled by the rc.conf, but I suppose that's how the maintainer wanted it done. If this is going to be how it is from now on, perhaps squid_enable should be mentioned in /etc/defaults/rc.conf ? This is a feature of rcNG -- instead of installing a sample startup file, which you have to copy into place, you instead get the rcNG-ified startup file, which you can turn on and customise by setting variables in /etc/rc.conf I don't think it would be feasible to add the default settings for all of the ports that use rcNG to /etc/defaults/rc.conf -- if you want to keep your ports stuff cleanly separated from the base systems, then add: rc_conf_files=/etc/rc.conf /etc/rc.conf.local /usr/local/etc/rc.ports.conf to your /etc/rc.conf, and put your ports related settings in there. The default rcNG startup script settings are documented in the scripts themselves. It might be an idea to make such ports register their default settings in /usr/local/etc/defaults/rc.ports.conf (for example) but I'm not entirely convinced that the benefit of doing so outweighs the effort required to set it up. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
squid-2.5.4_6 warning: port must be 1024
It seems squid can no longer bind to ports 1024 (as of 2.5.4_6). I've been binding to port 85 for ~2 years, and all of a sudden today my squid started crashing immediately after upgrading. I was getting this in my cache.log: 2004/01/16 23:52:43| commBind: Cannot bind socket FD 10 to 127.0.0.1:85: (13) Permission denied Anyhow, as soon as I changed the port to 8585, it started working again. So if you're experiencing problems with the new squid, double-check your port to be 1024. Hope this helps someone. :) -- Adam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: squid-2.5.4_6 warning: port must be 1024
On Sat, 17 Jan 2004 00:02:17 -0500 Adam McLaurin [EMAIL PROTECTED] wrote: It seems squid can no longer bind to ports 1024 (as of 2.5.4_6). I've been binding to port 85 for ~2 years, and all of a sudden today my squid started crashing immediately after upgrading. I was getting this in my cache.log: 2004/01/16 23:52:43| commBind: Cannot bind socket FD 10 to 127.0.0.1:85: (13) Permission denied Anyhow, as soon as I changed the port to 8585, it started working again. So if you're experiencing problems with the new squid, double-check your port to be 1024. Hope this helps someone. :) Also, keep in mind you'll need to append your rc.conf with: squid_enable=YES It does seem strange that a port's behaviour would be controlled by the rc.conf, but I suppose that's how the maintainer wanted it done. If this is going to be how it is from now on, perhaps squid_enable should be mentioned in /etc/defaults/rc.conf ? -- Adam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
