Seems like a bad Idea to mess with the server, when its only one workstation
that has a problem (and even on that workstation, its only the slack system
(not the suse, or the windows) that has a problem.
Jamie
On Saturday 22 March 2003 05:47 pm, Graham Forest wrote:
: On Sat, 22 Mar 2003 17:39:41 -0800
:
: Linux Rocks ! <[EMAIL PROTECTED]> wrote:
: > 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
:
: <snip>
:
: My idea was to kill inetd on the server, then starting standalone server
: processes (via /etc/init.d/sshd start type things, depending on distro, or
: possibly by running sshd manually), otherwise logging in my become rather
: difficult ^_^. There really shouldn't be a one minute delay, even when
: using inetd, so there's likely some other problem. Unfortunately, I haven't
: the slightest at what it could be (My general strategy is to avoid
: complexity, and a good portion of all problems with it - Openbox forever!).
: Maybe a bit of sacrafice to the Linux Gods is in order?
:
: Graham
--
When you say "I wrote a program that crashed Windows", people just stare at
you blankly and say "Hey, I got those with the system, *for free*".
-- Linus Torvalds
_______________________________________________
Eug-LUG mailing list
[EMAIL PROTECTED]
http://mailman.efn.org/cgi-bin/listinfo/eug-lug
