Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <385558D8.2544A53F@veritas.com>
Date: Mon, 13 Dec 1999 12:36:40 -0800
From: Bob McGowan <Robert DOT McGowan AT veritas DOT com>
Organization: VERITAS Software
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Cygwin <cygwin AT sourceware DOT cygnus DOT com>
Subject: signal error -3, Win32 error 317
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi, all,

I am using the cygwin tools to run UNIX developed test scripts in a
WinNT environment.  One of the scripts, every once in a while, will
generate the following error:

1617775739 -1867899777 [main] bash 7805 sig_send: error sending signal
-3 to pid 7805, semaphore 0x8C, Win32 error 317

The first two numbers and the PID values vary, but the signal number,
semaphore value and Win32 error number are consistently the same.

The event does not appear to cause any problem with the script itself,
since it continues to run.  I am curious if anyone can tell me what is
happening here.  Is there a bug that I have uncovered or am I just
pushing the limits of the system?

The basic operation of the the script is to copy a directory tree with
files from a source to a destination and compare the two trees.  If no
differences are found, delete the destination and repeat.  If there are
differences, exit.  The script uses a function to run the copy, compare,
delete sequence, which is put in the background.  There will be one or
more copies of this function running, depending on the load I want to
produce on the the hardware being tested.  The only difference from the
UNIX side (which I have used successfully for a several years) is that
there is no "dircmp" script available with cygwin, so I made a simple
one, also as a function, in the script itself.  The script uses 'find'
to generate the list of files to copy, 'cpio' to copy them using '-dmp'
options, the 'dircmp' function to check the copies, and 'rm -rf' to
delete them.

In this specific case, there are 3 copies of the top script running,
with 6 test directories each, a total of 18 copy/compare/delete cycles
running concurrently.  I can supply the script and my general setup if
needed.

-- 
Bob McGowan
Staff Software Quality Engineer
VERITAS Software
rmcgowan AT veritas DOT com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com