Re: RFD: cygwin ACLs: NFS or POSIX model: ease in adapting to CIFS ACLs?

2014-12-23 Thread Larry Hall (Cygwin)
On 12/21/2014 06:25 PM, Linda Walsh wrote: I seem to remember that the cygwin ACL's were based on NFS acls not the POSIX ACL's. From this snippet I read on the Samba list, it seems there are some "very difficult" [nightmarish] cases where NFS causes CIFS compatibility problems. Is this only NFS

Re: Exitcode is 0 when killing a cygwin initiated process via taskmanager

2014-12-23 Thread -
>> If it is similar in GNU/Linux we have a general problem I suppose. If it is >> a cygwin >> thing, it is a feature which behaves different to the real posix world?! > Cygwin is a POSIX environment executing within the Windows OS environment. > If things happen outside of the Cygwin environment

RE: Exitcode is 0 when killing a cygwin initiated process via taskmanager

2014-12-23 Thread cyg Simple
> > I scratch my head if we have a similar situation in GNU/Linux. > > If anything went havoc I so far supposed that exit code or abrupt script > breakdown (stop) cares about not doing nasty things. > > So at the moment if you consider the OS or a user kills a process with > Taskmanager we have

Re: SSHd configuration problems (System error 1376)

2014-12-23 Thread Ken Brown
On 12/23/2014 8:41 AM, Ilya Dogolazky wrote: Hi Ken ! 12/13/2014 02:30 PM, ext Ken Brown пишет: admingroup=$(/usr/bin/mkgroup -l | /usr/bin/awk -F: '{if ( $2 == "S-1-5-32-544" ) print $1;}') On my system this yields "Administrators". Apparently it yields "root" on your system. Any idea wh

Re: SSHd configuration problems (System error 1376)

2014-12-23 Thread Ilya Dogolazky
Hi Ken ! 12/13/2014 02:30 PM, ext Ken Brown пишет: admingroup=$(/usr/bin/mkgroup -l | /usr/bin/awk -F: '{if ( $2 == "S-1-5-32-544" ) print $1;}') On my system this yields "Administrators". Apparently it yields "root" on your system. Any idea why? I have the same error message as PolarSto

Re: Exitcode is 0 when killing a cygwin initiated process via taskmanager

2014-12-23 Thread -
Hi Marco, I agree and I didn't want to rant. I just consider robustness and I can not rely on or guarantee that cygwin kill ist used. (It is the user of the Windows machine being creative ;-) I scratch my head if we have a similar situation in GNU/Linux. If anything went havoc I so far supposed

Re: Exitcode is 0 when killing a cygwin initiated process via taskmanager

2014-12-23 Thread Marco Atzeri
On 12/23/2014 12:09 PM, - wrote: Using Taskmanager is brute force as cygwin dll can not act and correctly manage the exitcode Hi, thanks, but I do not agree. One element of the script was killed, not the hoöe script. It was not killed in the proper cygwin way. > It should be more robust.

Re: Exitcode is 0 when killing a cygwin initiated process via taskmanager

2014-12-23 Thread -
>> Using Taskmanager is brute force as cygwin dll can not act and correctly >> manage the exitcode Hi, thanks, but I do not agree. One element of the script was killed, not the hoöe script. It should be more robust. What I do now is: Read stdout of the program (rsync) and only if I got the righ

Link to poshbingo.com from cygwin.org

2014-12-23 Thread jonathanmilford866
Hi, My name is Jonathan Milford, and I’m an Seo Account Manager for poshbingo.com Due to the latest Google algorithm changes we are currently doing a lot of hard work to clean up a lot of the incoming links to our site to comply with Google’s quality guidelines. We detected this link comin