Re: need help with cygwin snapshot debugging

> Hmm. I don't see any reason for you to have included my message, > ignored it, and then used this thread to 1) reiterate observations you > made in another message and/or 2) discuss something unrelated to my > request. > > cgf I don't see any reason for your rude reply to me. Read your own mes

Re: need help with cygwin snapshot debugging

On Sun, May 14, 2006 at 06:06:28PM -0700, [EMAIL PROTECTED] wrote: >On Wed, May 10, 2006 at 02:01:35PM -0400, Christopher Faylor wrote: >> There are a few reported problems with the current snapshots that >> require some debugging: >> >> 1) http://cygwin.com/ml/cygwin/2006-04/msg00718.html >> >>

Re: need help with cygwin snapshot debugging

On Wed, May 10, 2006 at 02:01:35PM -0400, Christopher Faylor wrote: > There are a few reported problems with the current snapshots that > require some debugging: > > 1) http://cygwin.com/ml/cygwin/2006-04/msg00718.html > > I would appreciate knowing if anyone can duplicate 1) above and > I'd like

Re: Fwd: Got any 'fileno_unlocked'?

On Fri, May 12, 2006 at 12:49:36PM -0700, Brian Dessent wrote: > > It has nothing to do with file locking, but rather locking in the sense > of thread-safety. A programmer can call the _unlocked version of a > number of functions when he is sure that the application only has one > thread, and avo

Re: slowness issue between 20060309 and 20060313

On Sun, May 14, 2006 at 01:49:49PM -0700, [EMAIL PROTECTED] wrote: > On Sun, May 14, 2006 at 01:24:04PM -0700, [EMAIL PROTECTED] wrote: > > not even slowdown that could be explained by typical fork overhead, it's > > literally > > 200% the difference. > > > > >From 20060313 and any snapshot above

Cron execution

Hi all, I edited a users crontab, although I don’t understand why it's not executing... The crontab has an entry to backup every hour, yet the cronjob does not seem to get called. Can someone explain to me what im missing? Do I have to call it from the windows scheduler? Running WINXP SP2 With

WNOHANG & co in stdlib.h

Hi, Posix says that WNOHANG, WUNTRACED, WEXITSTATUS, WIFEXITED, WIFSIGNALED, WIFSTOPPED, WSTOPSIG, WTERMSIG should be defined in just like it is in . For now, cygwin doesn't do that; it should. Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: htt

Re: slowness issue between 20060309 and 20060313

On Sun, May 14, 2006 at 01:24:04PM -0700, [EMAIL PROTECTED] wrote: > not even slowdown that could be explained by typical fork overhead, it's > literally > 200% the difference. > > >From 20060313 and any snapshot above that, I see the exact same behavior. > >From any > below *and including* 2006

slowness issue between 20060309 and 20060313

I'm trying to debug a sever slowdown seen between 0309 and 0313 snapshots. I noticed this when upgrading to the latest and had to trace it back (part of the impetus for writing the script I mentioned earlier). It appears to affect all file operations within a shell, but not necessarily within a

a simple cygwin snapshot regression finding script i wrote in bash

I wrote this script to help people streamline testing snapshot issues when they identify an issue in a snapshot but do not necessarily know where the issue might have occured (for instance they do not iteratively keep up on snapshot releases). Based on the snapshots available at "http://www.cygwin.

Re: automake: 1.4, 1.5, and wrapper

On Fri, May 12, 2006 at 07:49:30PM -0400, Charles Wilson wrote: > Yaakov S (Cygwin Ports) wrote: ... > >3) In addition, it is possible to have a wrapper for automake with our > >setup. Gentoo has a similar setup, and uses this: > > > >http://www.gentoo.org/cgi-bin/viewcvs.cgi/*checkout*/sys-deve

Re: Cygwin CVS trailing dot problem

Hi Igor, Thanks for your reply and sorry for noting knowing the policy of PPIOSPE :-) Have a nice day. Joy Hi, Joy, . It is usually a bad idea to send email to random Cygwin mailing list participants, rather than asking on the Cygwin mailing list. I'm re

Python 2.4.1-1 time.altzone does not include DST offset

Python's time.altzone is equal to time.timezone, it should be time.timezone-3600 (for CEST) $ python -c 'import time; time.tzset(); print time.ctime(), \ time.daylight, time.timezone, time.altzone, time.tzname' Sun May 14 13:46:55 2006 1 -3600 -3600 (' ', ' ') Possible side effect of the b