Re: Cygwin outputting message to stderr on dofork EAGAIN failure even when Python exception is caught and handled

2024-06-18 Thread Dan Shelton via Cygwin
On Mon, 17 Jun 2024 at 18:03, Dale Lobb (Sys Admin) via Cygwin wrote: > > Greetings, Nicholas; > > > From: Cygwin On > > Behalf Of Andrey Repin via Cygwin > > Sent: Monday, June 17, 2024 2:58 AM > > To: Nicholas Williams ; cygwin@cygwin.com > > Cc: Andrey Repin > > Subject: EXTERNAL SENDER: Re:

Re: Cygwin outputting message to stderr on dofork EAGAIN failure even when Python exception is caught and handled

2024-06-18 Thread Nicholas Williams via Cygwin
Andrey and Dale, > On Jun 17, 2024, at 11:03, Dale Lobb (Sys Admin) > wrote: > > Greetings, Nicholas; > >> From: Cygwin > > On Behalf Of >> Andrey Repin via Cygwin >> Sent: Monday, June 17, 2024 2:58 AM >> To: Nicholas Williams >

cygwin runs three instances of rsync.exe at the same time

2024-06-18 Thread asdffdsa6132 via Cygwin
hello, thanks, first time poster, sorry if i mis-posted. when in run rsync.exe, in task manager, i see three instances running at the same time. in five years, my backup script runs native windows apps such as rclone.exe, restic.exe, fastcopy.exe, 7z.exe and never had this happen. now, i added

Issue regarding SFD_CLOEXEC. error: "''O_CLOEXEC' undeclared here (not in a function); did you mean 'FD_CLOEXEC'?"

2024-06-18 Thread christianon39--- via Cygwin
Hi, I am trying to build wlroots, but get this error in meson logs: Command line: `cc /home/Chris/wlroots/build/meson-private/tmprxphcsub/testfile.c -o /home/Chris/wlroots/build/meson-private/tmprxphcsub/output.obj -c -D_FILE_OFFSET_BITS=64 -O0 -std=c11` -> 1 stderr: In file included from /home

Sv: Issue regarding SFD_CLOEXEC. error: "''O_CLOEXEC' undeclared here (not in a function); did you mean 'FD_CLOEXEC'?"

2024-06-18 Thread christianon39--- via Cygwin
This is a test file I ran so that I didnt need to run the build every time for wlroots. Compiled to exe file with "gcc -o checko test.c". Needs to have a file just called testfile to work Fra: christiano...@outlook.com Sendt: tirsdag 18. juni 2024 17:07 Til: cygw

Re: Cygwin outputting message to stderr on dofork EAGAIN failure even when Python exception is caught and handled

2024-06-18 Thread Nicholas Williams via Cygwin
Dan, > On Jun 18, 2024, at 09:44, Dan Shelton via Cygwin wrote: > > On Mon, 17 Jun 2024 at 18:03, Dale Lobb (Sys Admin) via Cygwin > wrote: >> >> Greetings, Nicholas; >> >>> From: Cygwin On >>> Behalf Of Andrey Repin via Cygwin >>> Sent: Monday, June 17, 2024 2:58 AM >>> To: Nicholas Willia

Unknown Charge: Requesting Further Details

2024-06-18 Thread info--- via Cygwin
Hi there, I trust this message finds you well. I am writing to inquire about an unknown debit that has appeared on my bank account from your store. I do not have a record of making a order from your store in the recent past, and I am troubled that this may be an mistake. I would be grateful for

Re: cygwin runs three instances of rsync.exe at the same time

2024-06-18 Thread Sam Edge via Cygwin
On 18/06/2024 16:03, asdffdsa6132 via Cygwin wrote: hello, thanks, first time poster, sorry if i mis-posted. when in run rsync.exe, in task manager, i see three instances running at the same time. in five years, my backup script runs native windows apps such as rclone.exe, restic.exe, fastcopy

Re: cygwin runs three instances of rsync.exe at the same time

2024-06-18 Thread Sam Edge via Cygwin
On 19/06/2024 07:09, Sam Edge via Cygwin wrote: This is how rsync works. The executable forked from the command line runs up two communicating child processes to handle the 'from' and 'to' ends of the transfer. I forgot to say, this is how rsync works on any platform such as Linux or OS X or w