From: Rashi Singhal <singhal.rashi@gmail.com>
To: eply-to-list-only-lh@cygwin.com, cygwin@cygwin.com
Subject: Re: Cygwin 1.7-58 with windows 2008
Date: Tue, 23 Feb 2016 03:34:00 -0000 [thread overview]
Message-ID: <CAPCR6Q3vmSB2BnKdmjAqobQDOxVjU3GKE0J9q4eapkKirPO5Mg@mail.gmail.com> (raw)
In-Reply-To: <CAPCR6Q01AN+KuNySYE-pUAz=8m-vNA33Xq0yiB=ULkLYQYi7Yw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
Hi ,
We have call to "msgsnd" function that fails after processing 3 to 4 messages.
We tried both Block and NO Block mechanism (IPC_NOWAIT)
Also we changes configuration of cygserver.conf .This increases
message processing to 8-10 messages.But fails after that.
Attached is cygserver.conf file for reference:
On Mon, Feb 22, 2016 at 3:20 PM, Rashi Singhal <singhal.rashi@gmail.com> wrote:
> Hi ,
>
> Last version working with out application is 1.7.32. We tried with
> this version but problem remain same.
>
> With the latest version of cygwin (2.4.1 release) our program gives
> compilation error for Yacc and LEX modules.( We are checking on this)
>
> Please can you suggest something on EAGAIN issue
>
>
> On Wed, Feb 17, 2016 at 2:14 PM, Rashi Singhal <singhal.rashi@gmail.com> wrote:
>> We tried with latest version also . But problem remain same
[-- Attachment #2: cygserver.conf --]
[-- Type: application/octet-stream, Size: 5352 bytes --]
# cygserver.conf, Copyright(C) 2003, 2005 Red Hat Inc.
#
# Contains configurable parameters for the cygserver.
#
# The format of this file is easy. Lines beginning with a hash `#' are
# comments and ignored. Lines consisting of only whitespaces are ignored.
# Any other line is a setting for cygserver.
# A setting consists of a name/value pair, separated by whitespace.
# Each line must only consist of one name/value pair.
# Lines must not be longer than 1023 characters.
#
# Some settings can be overridden by a command line switch. If so, it's
# mentioned below.
#
# Settings which are commented out will use the default values. These are
# mentioned below, too.
# kern.srv.cleanup_threads: No. of cygserver threads used for cleanup tasks.
# Default: 2, Min: 1, Max: 16, command line option -c, --cleanup-threads
#kern.srv.cleanup_threads 16
kern.srv.cleanup_threads 16
# kern.srv.request_threads: No. of cygserver threads used to serve
# application requests.
# Default: 10, Min: 1, Max: 310, command line option -r, --request-threads
kern.srv.request_threads 310
# kern.srv.process_cache_size: No. of concurrent processes which can be handled
# by Cygserver concurrently.
# Default: 62, Min: 1, Max: 310, command line option -p, --process-cache
kern.srv.process_cache_size 310
# kern.srv.msgqueues: Determines whether XSI Message Queue support should be
# started, "yes" (or "true", "y", "t", "1") or "no" (or "false", "n", "f", "0").
# These values are valid for all binary type options.
# Default is "yes". Command line option -q, --no-msgqueues
kern.srv.msgqueues yes
# kern.srv.semaphores: Determines whether XSI Semaphore support should be
# started. Default is "yes". Command line option -s, --no-semaphores
kern.srv.semaphores yes
# kern.srv.sharedmem: Determines whether XSI Shared Memory support should be
# started. Default is "yes". Command line option -m, --no-sharedmem
kern.srv.sharedmem yes
# LOGGING
# kern.log.syslog: Determines whether logging should go to the syslog,
# Default is "yes", if stderr is no tty, "no" otherwise.
# Command line option -y, --syslog or -Y, --no-syslog.
kern.log.syslog no
# kern.log.stderr: Determines whether logging should go to stderr,
# Default is "yes", if stderr is a tty, "no" otherwise.
# Command line option -e, --stderr or -E, --no-stderr.
#kern.log.stderr no
# kern.log.level: Logging level. Valid values are 1 to 7 with a bigger
# value emitting more logging output. Default level is 6.
# Command line option -l, --log-level.
kern.log.level 7
# kern.log.debug: Determines whether debug output should be printed to stderr.
# Default is "no". Command line option -d, --debug
kern.log.debug no
# XSI message queue parameters.
#
# Each message is broken up and stored in segments that are msgssz bytes
# long. For efficiency reasons, this should be a power of two. Also,
# it doesn't make sense if it is less than 8 or greater than about 256.
# kern.ipc.msgseg: Maximum no. of message queue segments hold concurrently.
# Default: 2048, Min: 256, Max: 65535
kern.ipc.msgseg 512
# kern.ipc.msgssz: Size of segment in bytes. Must be a power of 2 value.
# Default: 8, Min: 8, Max: 1024
kern.ipc.msgssz 1024
# kern.ipc.msgmnb: Maximum no. of bytes in a single message queue.
# Default: 2048, Min: 1, Max: 65535
kern.ipc.msgmnb 65535
# kern.ipc.msgmni: Maximum no. of message queue identifiers hold concurrently.
# Default: 40, Min: 1, Max: 1024
#kern.ipc.msgmni 60
kern.ipc.msgmni 1024
# kern.ipc.msgtql: Maximum no. of messages hold concurrently.
# Default: 40, Min: 1, Max: 1024
#kern.ipc.msgtql 256
kern.ipc.msgtql 1024
# XSI semaphore parameters
# kern.ipc.semmni: Maximum no. of semaphore identifiers hold concurrently.
# Default: 10, Min: 1, Max: 1024
kern.ipc.semmni 1024
# kern.ipc.semmns: Maximum no. of semaphores hold concurrently.
# Default: 60, Min: 1, Max: 1024
kern.ipc.semmns 1024
# kern.ipc.semmnu: Total no. of undo structures hold by server.
# Default: 30, Min: 1, Max: 1024
kern.ipc.semmnu 200
# kern.ipc.semmsl: Maximum no. of semaphores per semaphore id.
# Default: 60, Min: 1, Max: 1024
kern.ipc.semmsl 1024
# kern.ipc.semopm: Maximum no. of operations per semop call.
# Default: 100, Min: 1, Max: 1024
kern.ipc.semopm 1024
# kern.ipc.semume: Maximum no. of undo entries per process.
# Default: 10, Min: 1, Max: 1024
kern.ipc.semume 1024
# kern.ipc.semvmx: Maximum value of a semaphore.
# Default: 32767, Min: 1, Max: 32767
kern.ipc.semvmx 32767
# kern.ipc.semaem: Maximum value to adjust on process exit.
# Default: 16384, Min: 1, Max: 32767
kern.ipc.semaem 32767
# XSI shared memory parameters
# kern.ipc.shmmaxpgs: Maximum pages available for XSI shared memory.
# Changing shmmaxpgs immediately affects setting SHMMAX. The relation
# between shmmaxpgs and SHMMAX is: SHMMAX = shmmaxpgs * getpagesize().
# Default: 8192, Min: 1, Max: 32767
kern.ipc.shmmaxpgs 32767
# kern.ipc.shmmni: Maximum number of shared memory segments, system wide.
# Default: 192, Min: 1, Max: 32767
kern.ipc.shmmni 32767
# kern.ipc.shmseg: Maximum number of shared memory segments per process.
# Default: 128, Min: 1, Max: 32767
kern.ipc.shmseg 256
[-- Attachment #3: Type: text/plain, Size: 218 bytes --]
--
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
next prev parent reply other threads:[~2016-02-23 3:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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-25 5:38 ` Fwd: " Mark Geisert
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
-- strict thread matches above, loose matches on Subject: below --
2016-02-17 5:53 Rashi Singhal
2016-02-17 6:50 ` Larry Hall (Cygwin)
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=CAPCR6Q3vmSB2BnKdmjAqobQDOxVjU3GKE0J9q4eapkKirPO5Mg@mail.gmail.com \
--to=singhal.rashi@gmail.com \
--cc=cygwin@cygwin.com \
--cc=eply-to-list-only-lh@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).