From: Michal Nazarewicz <mina86@tlen.pl>
To: query <query.cdac@gmail.com>
Cc: linux-admin@vger.kernel.org
Subject: Re: Preventing SSH timeouts . Some clarification needed
Date: Tue, 08 Jun 2010 21:48:44 +0200 [thread overview]
Message-ID: <87wru9e25f.fsf@erwin.mina86.com> (raw)
In-Reply-To: <AANLkTikcSKMXz4iFkGccOK5-Trp4lf7dOZa5l3NZw_4B@mail.gmail.com> (query's message of "Tue, 8 Jun 2010 20:40:39 +0530")
[-- Attachment #1: Type: text/plain, Size: 2246 bytes --]
> 2010/6/8 Michal Nazarewicz <mina86@tlen.pl>:
>> If “ifconfig” on one host gives you different IP addresses then the
>> other host see as incoming IP then you are behind NAT.
query <query.cdac@gmail.com> writes:
> Sorry , I failed to understand the above statement . But I have
> something in mind , I will try it tomorrow .
> From the source machine , I send a packet to remote host on a
> different network . Now If I capture packet on the remote host and
> it comes out to be different ip address than the source host , then
> probably I am behind NAT. These hosts are having private ip address.
Yes, that's what I've written. ;)
You run “ifconfig” an one machine at it will show you what's it's IP
address (there may be several interfaces). Then you connect from this
machine to the other machine and check the source address on the other
machine. Repeat for the other direction even thou, if you actually can
connect from one machine to the other then it is likely that the one you
are connecting to is not behind NAT.
> These hosts are not providing any Internet service and mainly
> responsible for processing around Gigabits of data . The processing
> continues for around 24 hours , During the processing , it utilizes
> around 100% CPU for around 4 hours and the connection drop happened
> during that time . Not sure what processig goes on during the time
> which takes all the CPU . The user we are talking here is the user
> under whom these processes runs .
If the processing takes so much time and is so CPU consuming I'd try
running it with nice, ie.: “nice -n 20 process-data” rather then plain
“process-data” command.
If the dropping in fact happens only while high CPU usage than maybe in
fact it is a culprit. By running the processing via nice it gets lower
priority (so in effect everything else gets higher priority in
comparison). This could help SSH get its desired CPU interval in time.
--
Best regards, _ _
.o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michal "mina86" Nazarewicz (o o)
ooo +--<mina86-tlen.pl>--<jid:mina86-jabber.org>--ooO--(_)--Ooo--
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-06-08 19:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 9:36 Preventing SSH timeouts . Some clarification needed query
2010-06-08 9:48 ` Michal Nazarewicz
[not found] ` <AANLkTimTjSOmbj_ac4iiUMaHRuvp1-ljW-FUGAQbb1qt@mail.gmail.com>
[not found] ` <87k4q9g31y.fsf@erwin.mina86.com>
2010-06-08 15:10 ` query
2010-06-08 19:48 ` Michal Nazarewicz [this message]
2010-06-09 5:33 ` query
2010-06-08 10:39 ` Glynn Clements
2010-06-08 15:10 ` query
2010-06-08 16:19 ` Glynn Clements
2010-06-09 6:44 ` query
2010-06-09 8:15 ` Adam T. Bowen
2010-06-09 10:14 ` Glynn Clements
[not found] ` <AANLkTimDS_IalexVnOKtOuKN8fz13rFumHV8TrjEGtph@mail.gmail.com>
[not found] ` <19471.47290.566464.539451@cerise.gclements.plus.com>
2010-06-10 6:02 ` query
2010-06-10 13:03 ` Glynn Clements
2010-06-10 16:35 ` query
2010-06-10 23:52 ` Glynn Clements
2010-06-11 7:22 ` query
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wru9e25f.fsf@erwin.mina86.com \
--to=mina86@tlen.pl \
--cc=linux-admin@vger.kernel.org \
--cc=query.cdac@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.