The current dante startup script provides incorrect details when no configuriation file is created. (see a. below) Currently the startup script places the "sockd" server into background immediately. Any errors in the configuration file are silently ignored in the startup process. (see b below) The sockd server currenly employs TCP keep-alive messages to maintain server contectivity. I suggest this is a bit unnecessary and it creates problems with dial-on-demand connections that should timeout. Reproducible: Always Steps to Reproduce: a) 1. rc-update add dante-sockd default 2. restart without a /etc/socks/sockd.conf b) 1. add some gibberish in the /etc/socks/sockd.conf file 2. /etc/init.d/dante-sockd restart Actual Results: a) the correct directory of the documentation should be specified. "info sockd" is not suggested to correctly make a configuration file. b) Errors are ignored and to all appearances "dante" was started correctly. Expected Results: a) better info is provided on generated on how to set up configuration files. b) The sockd displays that it has an error in its configuration file.
Created attachment 11166 [details] new startup script - files/dante-sockd-init For Changelog 26 Apr 2003; Daniel Black <dragonheart@tpg.com.au> files/dante-sockd-init : Corrected startup script to improve information given upon error conditions. Socket TCP keep alive disabled by default now.
I just spent some time pulling my hair out as to why dante-sockd wouldn't start properly on bootup, but it worked fine when I manually started it. This init.d script by Daniel actually shows me the error message that is causing my problem! Please consider merging it (it's been 7 months since it was entered here). Thanks.
Ben Lutgens <lamer@gentoo.org> no longer a dev.
For the ebuild, >=sys-apps/sed-4 is only a compile time dependacy
Created attachment 22427 [details, diff] dante-sockd-init.diff agriffis modifed the dante ebuild on Dec 8 - 2003 is he interested?
commited to CVS by myself now.
