* and this seems to have worked.
I speculate that some "bad" Cygwin ACLs got created at some point.
And maybe cacls wasn't deleting them?? That parts seems wierd. Maybe on
directories?
Possibly due to those two recent changes, or maybe user error, I don't know.
- Jay
From:
Cygwin making files inaccessible?
i.e. when Cygwin copies or writes to them, not random files.
C:\t>dir /s/b/a
C:\t>dir /q .
02/05/2022 04:11 AM BUILTIN\Administrators .
02/05/2022 04:11 AM NT SERVICE\TrustedInsta..
C:\t>cacls .
C:\t Everyone:(OI)(CI)F
C:\t>echo > 1
022 2:23 PM
To: Jay K ; cygwin@cygwin.com
Subject: Re: ExitProcess does not work in Cygwin?
Greetings, Jay K!
>> Just use POSIX exit(3)!
> I did switch my code:
> #ifdef __CYGWIN__
> exit(x);
> #else
> ExitProcess(x);
> #endif
> .
It is best to avoid Cygwin-s
January 13, 2022 5:19 PM
To: cygwin@cygwin.com
Cc: Jay K
Subject: Re: ExitProcess does not work in Cygwin?
On 2022-01-13 10:07, Kaz Kylheku (Cygwin) wrote:
> On 2022-01-13 05:40, Eliot Moss wrote:
>> On 1/13/2022 1:39 AM, Jay K wrote:
>>> ExitProcess does not work in Cygwin?
Ju
I don't know why I didn't get the reply in email, but this is representative of
the real world code.
- Jay
From: Jay K
Sent: Wednesday, January 12, 2022 6:27 AM
To: cyg...@sourceware.org
Subject: Re: proc_waiter: error on read of child wait pipe 0x0, Win32 error 6
Ok, here
ExitProcess does not work in Cygwin?
$ rm *.exe
# u is for Unix
# w is for Windows
$ cat u.c
#include
int main()
{
exit(1);
}
$ gcc u.c
$ ./a.exe
$ echo $?
1
=> as expected
$ cat w.c
#include
int main()
{
ExitProcess(1);
}
$ gcc w.c
$ ./a.exe
$ echo $?
0
=> not expected
$ uname -a
49909 [waitproc] 1 9269 proc_waiter: error on read of child wait pipe 0x0,
Win32 error 6
I understand I can workaround this, in that the use of threads is silly.
Is this invalid, to mix Win32 threads with cygwin system()?
- Jay
Fro
48ef0
"\260\324\005",
'cause i.e. it complicates any lifetime/management.
I do understand some of the problems here, like needing separate threads to
read stdout/stderr, if they are not equal.
- Jay
________
From: Jay K
Sent: Wednesday, January 12,
I get this a lot:
0 [waitproc] cm3 7641 proc_waiter: error on read of child wait pipe 0x0,
Win32 error 6
452 [waitproc] cm3 7641 proc_waiter: error on read of child wait pipe 0x0,
Win32 error 6
716 [waitproc] cm3 7641 proc_waiter: error on read of child wait pipe 0x0,
Win32 error
I have some desire to discuss fork.
I know it is an old and difficult topic.
I found this:
"Cygwin fork and RtlCloneUserProcess"
https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/afdf1b68-1f3e-47f5-94cf-51e397afe073/cygwin-fork-and-rtlcloneuserprocess?forum=windowsgeneraldevelopm
> I guess what we really need
> is to redefine fsblkcnt_t to become a 64 bit type. Oh well, this
> requires another backward compatibility hack, just like back when we
> switched to 64 bit off_t (Cygwin 1.5). Let's do it at the same time as
> we change sigset_t and time_t to 64-bits(with kno
> Not so much of an issue any more (still a bit curious about it, but). I
soon
> found that providing a '-lopengl32' link instead of
> '/cygdrive/c/Windows/System32/opengl32.dll' fixed the problem.
Linking to /cygdrive/c/windows/system32/whatever is "never" right.
It is not easy to e
On 64bit systems, /largeaddressaware gives 32bit processes 4GB of address
space, and no need to boot with a special option (well, other than using a
64bit OS!).
search for "largeaddressaware":
http://blogs.msdn.com/oldnewthing/archive/2005/06/01/423817.aspx
- Jay
---
> From: reply-to-list-only...@cygwin.com
> On 08/03/2009 12:11 AM, Jay K wrote:
>> I found that Interix sshd and WinSSHD work ok here.
>> So it is something specific to Cygwin.
> Are you talking about password or public key authentication? If the
> latter, Have you trie
Friend also found freesshd works and will use that.
So 3 out of 4 sshd work, Cygwin sshd is the only one that doesn't.
- Jay
[snip]
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation
I found that Interix sshd and WinSSHD work ok here.
So it is something specific to Cygwin.
- Jay
> From: jay.kr...@cornell.edu
> To: cygwin@cygwin.com
> Subject: running MS link.exe under Cygwin sshd?
> Date: Sat, 1 Aug 2009 04:50:15 +
>
>
> http://
http://social.msdn.microsoft.com/forums/en-US/vcgeneral/thread/eb49be0b-2a8c-4d55-8791-17e3cb1364c1
"
This issue is caused because cygwin does not implement a full login process. It
tries to impersonate, but it looks to me as if it does not make the necessary
call to LsaLogonUser. As a result,
17 matches
Mail list logo
