Normal behavior -- fixed - domain users showing up; remote ACLS working on SMB shares

2009-09-19 Thread Linda Walsh
Larry Hall (Cygwin) wrote: > On 09/15/2009 04:47 AM, Linda Walsh wrote: >> when I create my password and group files with mkpasswd and mkgroup, >> they put me in a group "513" -- and call it group 'None'. Yet I am >> in Users, and Admins -- and have no group none listed in my group list. > > 51

nice program for network usage?

2009-09-19 Thread Wes S
Is buried in the Cygwin project, a program like nice which keeps the system responsive when heavy cpu jobs are running except this is to use as much of bandwidth as possible unless other processes want bandwidth. I dags but came up empty, too many false positives. Thanks, Wes -- Problem repo

genisoimage with cygwin 1.7 generate STATUS_ACCESS_VIOLATION

2009-09-19 Thread andyg11
Hi, genisoimage 1.1.7.1 (CYGWIN) with cygwin1.dll v1007.0.0.0, 2009-09-11 01:25 throw following error whilte creating a large 2 GB iso file: 694 [main] genisoimage 3948 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 4487 [main] genisoimage 3948 open_stackdumpfile: Dumping s

typeset sem-failures in PD KSH v5.2.14 99/07/13.2

2009-09-19 Thread Paul McFerrin
Hello: The following simple script fails to produce a leading "0" on variable "nextnum". Am I doing something wrong or did I discover a bug? PD KSH v5.2.14 99/07/13.2 /home/paul.$ cat /lbin/testit2 #!/bin/pdksh n="06" typeset -L2 nextnum nextnum=`expr $n + 01` echo $nextnum /home/paul.$ /lb

Re: [1.7] sigwait bug (SIGCHLD delayed to a next regular signal)

2009-09-19 Thread Christopher Faylor
On Sat, Sep 19, 2009 at 10:43:19AM -0400, Christopher Faylor wrote: >I was explaining the problem to you. As I said, SIGCHLD is a signal >like any other signal and if you had tried to use a similar mechanism to >trap, say, SIGINT, you would have seen the same problem. ...and in fact, you did mask

Re: [1.7] sigwait bug (SIGCHLD delayed to a next regular signal)

2009-09-19 Thread Christopher Faylor
On Sat, Sep 19, 2009 at 10:31:58AM +, Waldemar Rachwal wrote: >On Fri, Sep 18, 2009 at 04:57:56PM +, Waldemar Rachwal wrote: >>Apparently, signals like SIGWINCH and SIGCHLD, which are a little bit >>special, need to be kicked by other signal to be eventually returned by >>sigwait(). >> >Chr

Re: [1.7] sigwait bug (SIGCHLD delayed to a next regular signal)

2009-09-19 Thread Waldemar Rachwal
Christopher Faylor cygwin.com> writes: > > Thanks for the test case. The problem has nothing to do with anything > "special" about SIGCHLD. It's a signal like any other signal. > I am not sure it's clear. With regard to sigwait() SIGCHLD like any other signal must not only be blocked, additi