public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Rashi Singhal <singhal.rashi@gmail.com>
To: cygwin@cygwin.com
Subject: Cygwin 1.7-58 with windows 2008
Date: Wed, 17 Feb 2016 05:53:00 -0000	[thread overview]
Message-ID: <CAPCR6Q3D0iaV3bnqen3dF1+X4g63KLnOB1BFQKjSgwkOTNpwEQ@mail.gmail.com> (raw)

Hi ,


I have a application  that is invoked multiple times. Each invocation
accesses shared memory for a performing task.

This all works with Cygwin1.3

Now We are using Cygwin 1.7-58 with windows 2008 after this The number
of attached processes keeps on increments and due to which system
resource gets full.

None of the process get detached from shared memory

With Cygwin 1.7-58 When I run through my application, it will give
successful response for  3 messages out 5 messages and my client
application hangs. My Error log file has recorded the following
statements:
CU-E-3404(3196):Unable to Send Communication Packet (CUP) on Queue.
msgsnd-E-3011(3196):EAGAIN No more processes..

Our application uses IPC functionalities for sending and receiving
messages from other application. I have made the following
configuration for message queue, shared memory and semaphore

MSGINFO:
MSGMAX:    4096
MSGMNI:    50
MSGTQL:    400
MSGMAP:    402
MSGMNB:    16384

SEMINFO:
SEMMNI:    200
SEMMNS:    128
SEMMNU:    150

SHMINFO:
SHMMNI:    100
SHMMAX:    2000000


So please... can any one suggest where m going wrong and please give
me the possible solutions for it.
Your help is really appreciated.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2016-02-17  5:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17  5:53 Rashi Singhal [this message]
2016-02-17  6:50 ` Larry Hall (Cygwin)
2016-02-17  8:44 Rashi Singhal
2016-02-17  9:09 ` Marco Atzeri
2016-02-22  9:50 ` Rashi Singhal
2016-02-22 11:21   ` Marco Atzeri
2016-02-23  3:34   ` Rashi Singhal
2016-02-23 14:01     ` Marco Atzeri
2016-03-04 16:40     ` Rashi Singhal
2016-03-09  8:00       ` Rashi Singhal
2016-03-09  8:16         ` Marco Atzeri
     [not found]         ` <CAPCR6Q2GdXd=EF7iAdP+xYT7UomLefLKgDm=be0oD=Wh64T_-g@mail.gmail.com>
2016-03-11  2:40           ` Rashi Singhal
2016-03-11  6:38             ` Mark Geisert
2016-03-17 11:19             ` Rashi Singhal
2016-03-17 11:47               ` Marco Atzeri
2016-03-18 16:15               ` Peter A. Castro
     [not found]                 ` <CAPCR6Q32VQeQLLjOC6t5UNs-AVtHYC_Er1ETdZHtYifbD6j3rA@mail.gmail.com>
     [not found]                   ` <alpine.LNX.2.00.1603231447150.6583@ming.fruitbat.org>
2016-03-24  4:20                     ` Fwd: " Rashi Singhal
2016-03-24 19:29                       ` Warren Young
2016-03-24 19:36                         ` Warren Young
2016-03-28  9:08                       ` Rashi Singhal
2016-03-28 10:50                         ` Andrey Repin
2016-03-28 11:06                           ` Rashi Singhal
2016-03-28 14:30                             ` Erik Soderquist
2016-03-29  2:47                       ` Rashi Singhal

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=CAPCR6Q3D0iaV3bnqen3dF1+X4g63KLnOB1BFQKjSgwkOTNpwEQ@mail.gmail.com \
    --to=singhal.rashi@gmail.com \
    --cc=cygwin@cygwin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).