OK, now its back again. I killed off inetd on the workstation, but still get
the delay :(
Killing it on the server caused the machine to refuse connections from any
computer (this is what I expected... no big surprise...)
somehow it has something to do with the slackware workstation... but what?
Jamie
On Saturday 22 March 2003 05:09 pm, Linux Rocks! wrote:
: Hmm... ok, I have inetd running on both the gateway box, and the
: workstation. I killed it on the workstation, and was able to connect right
: up. I then rebooted the workstation (not killing off inetd) and connected
: right up. Now I cant get get the delay, and Im totally unsure why! my only
: guess is somehow killing it off one time caused it to work now (even though
: inetd is running on both computers!)
:
: Jamie
:
: On Saturday 22 March 2003 03:53 pm, Graham Forest wrote:
: : On Sat, 22 Mar 2003 15:47:58 -0800
: :
: : Linux Rocks ! <[EMAIL PROTECTED]> wrote:
: : > I forgot to mention that once I make one telnet/ssh connection,
: : > subsequent connections pop right up (not wait), but if I close all
: : > connections, a new connection causes a long delay.
: : >
: : > Jamie
: :
: : <snip>
: :
: : (x)inetd? The delay could be caused by it having to launch a process, but
: : a minute seems a bit severe. I've had such delays on MacOSX, and it was
: : using inetd. Considering todays abundance of RAM, I personally prefer to
: : not use (x)inetd, and just use standalone servers.
: :
: : Graham
--
In most countries selling harmful things like drugs is punishable.
Then howcome people can sell Microsoft software and go unpunished?
-- Hasse Skrifvars, [EMAIL PROTECTED],
_______________________________________________
Eug-LUG mailing list
[EMAIL PROTECTED]
http://mailman.efn.org/cgi-bin/listinfo/eug-lug
