I am just started looking at this problem and It was reported to  me
today. What is happining is that the NDM people try to shudown the process
and it notice that it can;t
 not bring down NDM when there are "CLOSE-WAIT"  on the port 1363/1364.  I
don't think  C:D  is in a  zombie state.  Is it possible of  change the
value of
 net.ipv4.tcp_fin_timeout   to go around  this problem?






             "Fargusson.Alan"
             <[EMAIL PROTECTED]
             tb.ca.gov>                                                 To
             Sent by: Linux on         LINUX-390@VM.MARIST.EDU
             390 Port                                                   cc
             <[EMAIL PROTECTED]
             IST.EDU>                                              Subject
                                       Re: "Close-wait"

             11/15/2006 03:54
             PM


             Please respond to
             Linux on 390 Port
             <[EMAIL PROTECTED]
                 IST.EDU>






I am not sure I understand your description of the problem.  Are you are
saying that you have a process in a zombie state, and you have a socket in
the close-wait state?

If that is the case: the two are unrelated.  Sockets can be in the
close-wait state for a long time, but this will not hold a process in the
zombie state.  A process stays in the zombie state until the parent process
waits for it.  If you have a process in a zombie state for a long period of
time it means there is a bug in the parent process.

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Eddie Chen
Sent: Wednesday, November 15, 2006 12:06 PM
To: LINUX-390@VM.MARIST.EDU
Subject: "Close-wait"


   I am currently run NDM  or  Connect Direct on Linux.

   The problem  is  when  it;'s  in  the "close-wait"  state, we can;t not
kill  the process and it seems to be in  the zombie state. The solution is
re-boot.

    I am think of  using  one of the User Exit, which is written in C and
force a  termination of all parents processor by killing myself.

    The question is there are way of getting out of this "close-wait" state
and then kill the process.
     And is it possible  of  using the USER EXIT that will kill all the
parents process?

      Thanks.


-----------------------------------------
This message and its attachments may contain  privileged and
confidential information.  If you are not the intended recipient(s),
you are prohibited from printing, forwarding, saving or copying this
email.  If you have received this e-mail in error, please immediately
notify the sender and delete this e-mail and its attachments from your
computer.

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390



-----------------------------------------
This message and its attachments may contain  privileged and
confidential information.  If you are not the intended recipient(s),
you are prohibited from printing, forwarding, saving or copying this
email.  If you have received this e-mail in error, please immediately
notify the sender and delete this e-mail and its attachments from your
computer.

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to