First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 19988
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: SpanKY <vapier@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Daniel Black <dragonheart@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
dante-sockd new startup script - files/dante-sockd-init text/plain Daniel Black 2003-04-26 03:02 0000 946 bytes Details
dante.diff dante-sockd-init.diff patch Daniel Black 2003-12-18 23:51 0000 728 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 19988 depends on: Show dependency tree
Show dependency graph
Bug 19988 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2003-04-26 02:56 0000
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.

------- Comment #1 From Daniel Black 2003-04-26 03:02:32 0000 -------
Created an attachment (id=11166) [edit]
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.

------- Comment #2 From Phil Sweeney 2003-12-18 04:33:31 0000 -------
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.

------- Comment #3 From Daniel Black 2003-12-18 16:16:59 0000 -------
Ben Lutgens <lamer@gentoo.org> no longer a dev.

------- Comment #4 From Daniel Black 2003-12-18 18:04:30 0000 -------
For the ebuild, >=sys-apps/sed-4 is only a compile time dependacy

------- Comment #5 From Daniel Black 2003-12-18 23:51:40 0000 -------
Created an attachment (id=22427) [edit]
dante-sockd-init.diff

agriffis modifed the dante ebuild on Dec 8 - 2003 is he interested?

------- Comment #6 From Robin Johnson 2003-12-23 02:48:28 0000 -------
commited to CVS by myself now.

First Last Prev Next    No search results available      Search page      Enter new bug