Re: telnetd process getting terminated

On 28 Nov 2006 05:31:36 -0800
"koole" <KeerthiPrasad.ma@xxxxxxxxx> wrote:

Please don't top post. I fixed it so you would see how easy a properly
quoted reply reads.

Casper H. S. *** wrote:
"koole" <KeerthiPrasad.ma@xxxxxxxxx> writes:

On similar env with the same capacity,same memory i found telnetd
process getting terminated.

Define "similar"; there is nothing in Solaris that does this.
(except the growing of te stack which is unlikely to happen in
steady state telnet)

I would not exclude a bug that causes this (severe memory
starvation), but there is nothing that does this.

I mean to say on Similar memory,capacity,load the performance of other
flavours like AIX,Redhat were better/good compared to solaris.

That's a pretty fuzzy metric. Were these systems running the same mix
of applications?

All the user sessions were active.

What do you mean by this? All the users allowed by the application, or
all the users your box could take? How many exactly are you talking
about?

If idle connection die after a time with "connection refused", then
there's likely some middle box (firewall, gateway) which causes
this behaviour.

there are no firewall issues,before 3 hrs 4 hrs before u r able to
login

I guess "u r" is "you are"? Do you mean that it takes 3 to 4 hours
between you typing your login and password that you get a prompt back?

when you are giving the load its getting terminated.

Can you explain this a bit better?

What do you mean by "giving the load"?

What is getting terminated? The "getting the load program" or the
session?


It is also possible that the system runs a program which terminates
long running and/or idle sessions.

There is no script running which will kill idle sessions(user script)

Such a program is not required. With the appropriate setting most
shells will terminate when idle for a while.

Please rest assured that there is nothing intrinsic to Solaris that
will make it terminate programs under extreme load.

You'll need to give a lot more details (and be a lot less accusatory)
if you want to get real help. Information on the system (processor,
memory, IO etc), the workload (is it running a database, how many
users, or whatever you believe is relevant), the network (you might
have a duplex mismatch on your NIC), etc. A very detailed description
of what you are experiencing (not what you _think_ is happening) is of
course also required.

Instead of assuming that Solaris has such obvious problems (and that
you're the first bright spark to discover this), try and approach the
problem with an open mind.

--
Stefaan A Eeckels
--
A business that makes nothing but money is a poor kind of business.
-- Henry Ford
.