Re: arc4random does not reseed after using fork()

Hi Johnothan, On Jan 26 22:06, Johnothan King via Cygwin wrote: > Hello, > > While testing ksh93u+m's recently added SRANDOM variable[1], I have > discovered a bug in Cygwin's arc4random function. After using fork(), > arc4random does not reseed itself, which causes the results to become >

Re: cygwin 3.4.10-1

On Jan 27 10:27, Marco Atzeri via Cygwin-apps wrote: > On 29/11/2023 15:08, Corinna Vinschen via Cygwin-announce wrote: > > The following packages have been uploaded to the Cygwin distribution: > > > > * cygwin-3.4.10-1 > > * cygwin-devel-3.4.10-1 > > * cygwin-d

Re: Setting process command name in forked process

On Jan 26 18:35, Steve Beck via Cygwin wrote: > Thanks so much for the reply, Anton! Really appreciate it. > > I tried what you proposed. Here is the code trying both ways > (overwriting what is referenced by __argv[0] and then reassigning the > reference). I compile this code (foo.c) simply

Re: Possiblly bug of cygwin1.dll

On Jan 24 14:05, Corinna Vinschen via Cygwin wrote: > On Jan 24 20:55, Takashi Yano via Cygwin wrote: > > On Mon, 22 Jan 2024 19:24:52 -0800 > > Kaz Kylheku wrote: > > > In real systems, the static distinction has no meaning. > > > > > >

Re: Possiblly bug of cygwin1.dll

On Jan 24 20:55, Takashi Yano via Cygwin wrote: > On Mon, 22 Jan 2024 19:24:52 -0800 > Kaz Kylheku wrote: > > In real systems, the static distinction has no meaning. > > > > This code can be inside a shared library: > > > >static pthread_mutex_t g_lock = PTHREAD_MUTEX_INITIALIZER; > > > >

bash 5.2.21-1

The following packages have been uploaded to the Cygwin distribution: * bash-5.2.21-1 * bash-devel-5.2.21-1 -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** The easiest way to unsubscribe is to visit , and click 'Unsubscribe'. If

Re: Add ability to hide non-standard itoa/utoa() in stdlib.h ?

On Jan 22 16:47, Christian Franke via Cygwin wrote: > Busybox does not build OOTB on Cygwin due to the addition of itoa/utoa() to > newlib in 2014: > https://cygwin.com/git/?p=newlib-cygwin.git;a=commit;h=32c96dd > > This is because Busybox use local functions with same name but different >

Re: Possiblly bug of cygwin1.dll

On Jan 22 13:41, ASSI via Cygwin wrote: > Corinna Vinschen via Cygwin writes: > > However, I don't find this in the standards. pthread_once is neither > > one of the required cancellation points, nor one of the optional > > cancellation points. > > The initializer c

Re: Possiblly bug of cygwin1.dll

On Jan 22 20:16, Takashi Yano via Cygwin wrote: > On Mon, 22 Jan 2024 10:57:48 +0100 > Corinna Vinschen wrote: > > On Jan 22 10:25, Corinna Vinschen via Cygwin wrote: > > > On Jan 22 12:30, Takashi Yano via Cygwin wrote: > > > > PATCH2: (for cygwin) > > >

Re: Possiblly bug of cygwin1.dll

On Jan 22 20:06, Takashi Yano via Cygwin wrote: > On Mon, 22 Jan 2024 10:25:28 +0100 > Corinna Vinschen wrote: > > On Jan 22 12:30, Takashi Yano via Cygwin wrote: > > > PATCH2: (for cygwin) > > > Avoid handle leak caused when non-static pthread_once_t is initialized > > > with PTHREAD_ONCE_INIT >

Re: Possiblly bug of cygwin1.dll

On Jan 22 10:25, Corinna Vinschen via Cygwin wrote: > On Jan 22 12:30, Takashi Yano via Cygwin wrote: > > PATCH2: (for cygwin) > > Avoid handle leak caused when non-static pthread_once_t is initialized > > with PTHREAD_ONCE_INIT > > diff --git a/winsup/cygwin/thread.c

Re: cygwin utils can access directory and its contents, but W10 utils claim to have no access, why?

On Jan 21 22:18, John Ruckstuhl via Cygwin wrote: > I am seeing a weird phenomenon, hopefully someone can illuminate and teach. > Or point me to an archived thread. > > I have some folders that Cygwin utils can readily access, > but W10 utils claim to have no access to. > It feels as if > * the

Re: Possiblly bug of cygwin1.dll

On Jan 22 12:30, Takashi Yano via Cygwin wrote: > PATCH2: (for cygwin) > Avoid handle leak caused when non-static pthread_once_t is initialized > with PTHREAD_ONCE_INIT > diff --git a/winsup/cygwin/thread.cc b/winsup/cygwin/thread.cc > index 7bb4f9fc8..127569160 100644 > ---

Re: Possiblly bug of cygwin1.dll

On Jan 19 22:44, Takashi Yano via Cygwin wrote: > Hi, > > I might find the bug of cygwin1.dll (including 3.4.x, 3.5.0 (TEST)). > The following test case (c++ code) causes handle leak. > > This issue is reproducible with both g++ and clang++. > However, it does not happen in Linux environment. >

Re: Package request: ms-nfs41-client

On Jan 18 06:52, Cedric Blancher via Cygwin wrote: > Good morning! > > Could Cygwin package the ms-nfs41-client (NFSv4 client with Cygwin > support), please? A few points: - There is no person called "Cygwin", really. We're *all* volunteers here. So if you want to get a certain package into

Re: How to test Cygwin 3.5 using github actions

On Jan 17 12:27, Glenn Strauss via Cygwin wrote: > On Wed, Jan 17, 2024 at 12:44:32PM +0100, Corinna Vinschen via Cygwin wrote: > > Hi folks, > > > > we're planning to release Cygwin 3.5 end of this month (Jan 2024) if > > nothing serious crops up. > > W

Cygwin 3.5 is coming soon, please test!

Hi folks, we're planning to release Cygwin 3.5 end of this month (Jan 2024) if nothing serious crops up. --- One major change in this release is dropping Windows 7, Windows 8, Windows Server 2008 R2, and Windows Server 2012

[ANNOUNCEMENT] Cygwin 3.5 is coming soon, please test!

Hi folks, we're planning to release Cygwin 3.5 end of this month (Jan 2024) if nothing serious crops up. --- One major change in this release is dropping Windows 7, Windows 8, Windows Server 2008 R2, and Windows Server 2012

Re: Cygwin tools to read/write NTFS alternate data streams?

On Jan 12 10:24, Cedric Blancher via Cygwin wrote: > On Thu, 11 Jan 2024 at 17:41, Corinna Vinschen via Cygwin > wrote: > Aside from that, I volunteer with testing of O_XATTR, on demand with 1 > or 2 students too. Yup, I'm volunteering for testing, too. Now we just have to f

Re: Cygwin tools to read/write NTFS alternate data streams?

On Jan 11 15:00, Martin Wege via Cygwin wrote: > On Mon, Jan 8, 2024 at 3:11 PM Corinna Vinschen via Cygwin > wrote: > so this is IMO OK. Yeah, but... It's not just an open flag, it requires extending functionality of other APIs and, for full support, tools, see https://docs.orac

Re: Cygwin generates syscalls for *.lnk files on filesystems with native symlink support?

On Jan 8 14:17, Jeffrey Altman via Cygwin wrote: > On 1/8/2024 1:44 PM, matthew patton via Cygwin wrote: > > > Cygwin does not create symlinks as junctions.  No idea where you got that > > > idea. > > $ echo $CYGWINwinsymlinks:nativestrict > > $ /usr/bin/ln -s default.GGG6q test1 > > 01/08/2024 

Re: Cygwin generates syscalls for *.lnk files on filesystems with native symlink support?

On Jan 8 17:11, matthew patton via Cygwin wrote: > > For instance: Getting rid of .lnk files isn't easy with backward  > >compatibility in mind. > screw backward compatability! :)Why carry around bandaids on bandaids > for an OS that is 10 years out of support? We're using .lnk files for FIFOs.

Re: /dev/u?random implementation

On Dec 20 16:32, Jim Garrison via Cygwin wrote: > I dug around in the Cygwin doc looking for details on how /dev/random > and /dev/urandom are implemented, but came up empty. Is this > documented anywhere? Not documented as such, it's a "use the source, luke" kind of information. /dev/random is

Re: rfe: CYGWIN fslinktypes option? Re: Catastrophic Cygwin find . -ls, grep performance on samba share compared to WSL

On Dec 24 01:47, Roland Mainz via Cygwin wrote: > On Thu, Dec 21, 2023 at 9:32 PM Kaz Kylheku via Cygwin > wrote: > > On 2023-12-21 04:16, Martin Wege via Cygwin wrote: > > > On Wed, Dec 20, 2023 at 6:21 PM Kaz Kylheku via Cygwin > > > wrote: > [snip] > > > The root cause is IMO the extra Win32

Re: Sparse file support for SMB by default? Re: Comment about "Cygwin: sparse support: enable automatic sparsifying of files on SSDs", extend feature to VMware/qemu disks?

On Dec 18 12:10, Cedric Blancher via Cygwin wrote: > On Wed, 6 Dec 2023 at 10:39, Corinna Vinschen via Cygwin > wrote: > > Basically, with 3.4, you always have to set the "sparse" mount option, > > with 3.5, on local SSDs you don't. I don't see a problem here. > &

Re: Cygwin tools to read/write NTFS alternate data streams?

On Dec 18 18:47, Martin Wege via Cygwin wrote: > On Fri, Dec 1, 2023 at 10:52 AM Corinna Vinschen via Cygwin > wrote: > > > > On Nov 30 04:55, Martin Wege via Cygwin wrote: > > > Hello, > > > > > > Does Cygwin have tools (modified /usr/bin/dd ?) to

Re: Cygwin generates syscalls for *.lnk files on filesystems with native symlink support?

On Dec 18 13:04, Cedric Blancher via Cygwin wrote: > On Fri, 1 Sept 2023 at 13:00, Corinna Vinschen via Cygwin > wrote: > > > > On Sep 1 06:23, Cedric Blancher via Cygwin wrote: > > > Good morning! > > > > > > During a Cygwin 3.4.8-1.x86_64 debugging

Re: Automatic announcement generation by calm

On Jan 7 16:12, Jon Turney via Cygwin-apps wrote: > This is an experimental facility, currently only available for packages > deployed from the build service [1] (that is, not for self-built packages > uploaded with 'cygport up' via sftp) > > When the token "announce" is present for a build job

Re: [EXTERNAL] Re: getVolInfo question

On Dec 7 19:53, Corinna Vinschen via Cygwin wrote: > On Dec 7 18:02, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: > > Thank you for your prompt reply! > > > > > TRIM is only enabled on a filesystem, if the underlying drive > > > actually supports TR

Re: [EXTERNAL] Re: getVolInfo question

On Dec 7 18:02, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: > Thank you for your prompt reply! > > > TRIM is only enabled on a filesystem, if the underlying drive > > actually supports TRIM. The majority of SSDs support it, but not > > necessarily all SSDs. > > > > The above values,

Re: getVolInfo question

On Dec 7 18:04, Corinna Vinschen via Cygwin wrote: > On Dec 7 15:35, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: > > Hi Corinna, > > > > I have a question about this tool getVolInfo that has recently "made the > > news". > > > >

Re: getVolInfo question

On Dec 7 15:35, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: > Hi Corinna, > > I have a question about this tool getVolInfo that has recently "made the > news". > > Just updated my version to the latest and tried it on my drive C:, and > specifically this is what bugs me: > > $

Re: Sparse file support for SMB by default? Re: Comment about "Cygwin: sparse support: enable automatic sparsifying of files on SSDs", extend feature to VMware/qemu disks?

On Dec 7 17:42, Shaddy Baddah via Cygwin wrote: > Hi Corinna, > > On 6/12/2023 8:38 pm, Corinna Vinschen via Cygwin wrote: > > > If you want to see if a filesystem supports that flag, just use the > > /usr/lib/csih/getVolInfo tool: > > > >$ /usr/lib/

Re: Sparse file support for SMB by default? Re: Comment about "Cygwin: sparse support: enable automatic sparsifying of files on SSDs", extend feature to VMware/qemu disks?

On Dec 6 10:38, Corinna Vinschen via Cygwin wrote: > Again, the filesystem doesn't matter. It either sets the > FILE_SUPPORTS_SPARSE_FILES flag or not, as simple as that. > > If it does, you can create sparse files with chattr +S, or you can rely > on the lseek/ftruncate/

Re: Sparse file support for SMB by default? Re: Comment about "Cygwin: sparse support: enable automatic sparsifying of files on SSDs", extend feature to VMware/qemu disks?

On Dec 6 09:49, Cedric Blancher via Cygwin wrote: > On Fri, 1 Dec 2023 at 11:43, Corinna Vinschen via Cygwin > VMware emulates NVME SSD these days, so this should work, yes? It doesn't matter, see below. > Primary concern is how to detect whether sparse file support is ON in

Re: Cygwin api to punch a hole into a file?

On Dec 5 15:47, Thomas Wolff via Cygwin wrote: > > Am 05/12/2023 um 15:40 schrieb Thomas Wolff via Cygwin: > > Am 05/12/2023 um 14:53 schrieb Corinna Vinschen via Cygwin: > > > On Dec  5 07:36, Thomas Wolff via Cygwin wrote: > > > > > > > > Am 01.

Re: Cygwin api to punch a hole into a file?

On Dec 5 07:36, Thomas Wolff via Cygwin wrote: > > > Am 01.12.2023 um 12:02 schrieb Corinna Vinschen via Cygwin: > > On Dec 1 11:22, Cedric Blancher via Cygwin wrote: > > > Not all filesystems have a 128k block/stripe size, and certainly most > > > filesystem

Re: Maximum path and path element length, Win32 vs Cygwin vs SFU?

On Dec 3 17:45, Cedric Blancher via Cygwin wrote: > Good evening! > > What is the maximum path length and path element (single file, dirname > length) in Win32 API, https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation > Cygwin APIs on Windows 11, NAME_MAX is 255

Re: Cygwin api to punch a hole into a file?

On Dec 1 11:22, Cedric Blancher via Cygwin wrote: > I see the value of 128k (128*1024 bytes) quite often in your sparse > file commits. Yes, but they have been removed. Read the patches again, especially commit 65831f88d6c4. > Can you please make this value a per filesystem tunable? No,

Re: Comment about "Cygwin: sparse support: enable automatic sparsifying of files on SSDs", extend feature to VMware/qemu disks?

On Dec 1 11:12, Cedric Blancher via Cygwin wrote: > Good morning! > > Small comment about 3.5.0 commit "Cygwin: sparse support: enable > automatic sparsifying of files on SSDs" > https://cygwin.com/git/?p=newlib-cygwin.git;a=commit;h=832e91422c4ae9b2dcd0c307779f3dd53ee9c0ac > > Can this

Re: Cygwin mount limited to 64 mounts, even for UNC paths?

On Dec 1 04:55, Andrey Repin via Cygwin wrote: > Greetings, Martin Wege! > > > Cygwin mount(1) is (per docs) limited to 64 mounts. Why was that > > limitation chosen, and does it apply even if I create bind mounts to > > UNC paths (not DOS letters)? DOS letters might be restricted by the > >

Re: Cygwin tools to read/write NTFS alternate data streams?

On Nov 30 04:55, Martin Wege via Cygwin wrote: > Hello, > > Does Cygwin have tools (modified /usr/bin/dd ?) to read/write NTFS > alternate data streams? No. As you know, the colon is translated to a normal filename character, and there's no POSIX-like API to expose ADS raw to user space. There

Re: "Lazy" bind mounts?

On Nov 30 04:53, Martin Wege via Cygwin wrote: > Hello, > > if I do a mount -o bind //foo/bar/baz /mnt the UNC path //foo/bar/baz > is evaluated immediately, i.e. the network share //foo/bar/baz is > "mounted" immediately. > > Is it possible to mount //foo/bar/baz only the first time someone

Re: Cygwin UNC path conversion functions?

On Nov 30 04:44, Martin Wege via Cygwin wrote: > Hello, > > does Cygwin have UNC path conversion functions, for example UNC path > to DOS mount letter, UNC path to file URL? Neither Cygwin nor Windows really care for that when using paths. Either you use a drive letter or you use an UNC path,

cygwin 3.4.10-1

The following packages have been uploaded to the Cygwin distribution: * cygwin-3.4.10-1 * cygwin-devel-3.4.10-1 * cygwin-doc-3.4.10-1 Bug Fixes - - Fix missing term in __cpuset_zero_s() prototoype in sys/cpuset.h. Addresses:

Re: Cygwin api to punch a hole into a file?

On Nov 24 12:01, Corinna Vinschen via Cygwin wrote: > On Nov 23 23:36, Cedric Blancher via Cygwin wrote: > > Linux has fallocate(fd, FALLOC_FL_PUNCH_HOLE|FALLOC_FL_KEEP_SIZE, ...) > > to punch a hole into a file, i.e. deallocate the blocks given and make > > the file a "s

Re: Cygwin api to punch a hole into a file?

On Nov 23 23:36, Cedric Blancher via Cygwin wrote: > Linux has fallocate(fd, FALLOC_FL_PUNCH_HOLE|FALLOC_FL_KEEP_SIZE, ...) > to punch a hole into a file, i.e. deallocate the blocks given and make > the file a "sparse file". We don't support the Linux-specific fallocate(2) call, only ftruncate(2)

Re: Set localisation locale of Windows netstat?

On Nov 23 00:25, Cedric Blancher via Cygwin wrote: > Good morning! > > How can I set the localisation locale of Windows netstat cmd from > Cygwin? LC_ALL=C does not help, a French or German Windows will use > French or German language still Cygwin has no influence on how non-Cygwin tools are

Re: Capturing a Cygwin instance from another PC

On Nov 22 23:44, Cedric Blancher via Cygwin wrote: > On Wed, 22 Nov 2023 at 17:15, Eliot Moss via Cygwin wrote: > > > > On 11/22/2023 10:43 AM, Bill Stewart via Cygwin wrote: > > > On Wed, Nov 22, 2023 at 7:53 AM Jose Isaias Cabrera wrote: > > > > > > I have a new Win11 PC, and I wanted to

Re: binfmt support in Cygwin?

On Nov 22 23:52, Cedric Blancher via Cygwin wrote: > On Tue, 26 Sept 2023 at 07:15, Cedric Blancher > wrote: > > > > Good morning! > > > > Does Cygwin support something like Linux binfmt, to register new binary > > types? > > > > Goal would be to recognise python compiled code, or > >

Re: Cygwin tool to differ junctions from soft links?

On Nov 17 06:54, Thomas Wolff via Cygwin wrote: > > > Am 16.11.2023 um 21:30 schrieb Brian Inglis via Cygwin: > > On 2023-11-16 11:55, matthew patton via Cygwin wrote: > > > On Thursday, November 16, 2023 at 03:50:24 AM EST, Andrey Repin wrote: > > > > > Does Cygwin have a command line tool

Re: rand is not ISO C compliant in Cygwin

On Nov 14 12:52, Bruno Haible wrote: > Corinna Vinschen wrote: > > > My understanding of this paragraph is: > > > - If an application wants 1., they can use rand_r with SEED pointing > > > to a global variable. > > > - If an application wants 2., they can use rand_r with SEED pointing > >

Re: rand is not ISO C compliant in Cygwin

On Nov 13 17:14, Glenn Strauss wrote: > On Mon, Nov 13, 2023 at 10:33:48PM +0100, Bruno Haible via Cygwin wrote: > > POSIX does not have these two sentences, but instead has: > > > > "The rand() function need not be thread-safe." > > I read the above as requiring *reentrancy*, but not

Re: rand is not ISO C compliant in Cygwin

Hi Bruno, On Nov 13 22:33, Bruno Haible via Cygwin wrote: > Corinna Vinschen wrote: > > https://pubs.opengroup.org/onlinepubs/9699919799/functions/rand.html > > [...] > > With regard to rand(), there are two different behaviors that may be > > wanted in a multi-threaded program: > > > > 1.

Re: random is not multithread-safe in Cygwin

On Nov 13 19:04, Bruno Haible via Cygwin wrote: > Corinna Vinschen wrote: > > > And indeed glibc, musl libc, AIX, Android, and even NetBSD implement it > > > in a > > > multithread-safe way. > > > > Our code is from FreeBSD, originally. I checked the latest code from > > FreeBSD. It doesn't

Re: rand is not ISO C compliant in Cygwin

On Nov 13 15:38, Corinna Vinschen wrote: > On Nov 13 15:25, Bruno Haible wrote: > > Corinna Vinschen wrote: > > > The rand() function would still not use locking but AFAICS that's > > > not actually required by POSIX or ISO C. > > > > Correct. Those who want an MT-safe rand-like function need to

Re: random is not multithread-safe in Cygwin

Hi Bruno, On Nov 10 17:19, Bruno Haible via Cygwin wrote: > The function 'random' is, unlike 'rand', not marked as not MT-safe in POSIX > [1][2]. Thus it must be multithread-safe [3]: > "Each function defined in the System Interfaces volume of POSIX.1-2017 >is thread-safe unless explicitly

Re: rand is not ISO C compliant in Cygwin

On Nov 13 15:25, Bruno Haible wrote: > Corinna Vinschen wrote: > > The rand() function would still not use locking but AFAICS that's > > not actually required by POSIX or ISO C. > > Correct. Those who want an MT-safe rand-like function need to use random(), > not rand(). FTR, we have to differ

Re: rand is not ISO C compliant in Cygwin

[redirecting to the newlib mailing list] This is long-standing code in newlib, not actually inside Cygwin. On Nov 10 21:19, Bruno Haible via Cygwin wrote: > ISO C 23 § 7.24.2.1 and 7.24.2.2 document how rand() and srand() are > expected to behave. In particular: > "The srand function uses the

openssh 9.5p1-1

The following packages have been uploaded to the Cygwin distribution: * openssh-9.5p1-1 OpenSSH is a program for logging into a remote machine and for executing commands on a remote machine. It can replace rlogin and rsh, providing encrypted communication between two machines.

Re: feraiseexcept does not raise traps in Cygwin

Hi Bruno, On Oct 25 11:21, Bruno Haible via Cygwin wrote: > Hi, > > Seen on > - Cygwin 3.4.6 or 2.9.0 on x86_64. > - Cygwin 2.9.0 on i386. > > According to ISO C 23 § 7.6.4.3 > "The feraiseexcept function attempts to raise the supported floating-point >exceptions represented by its

Re: NFS mkfifo support in cygwin 3.5.0

On Sep 8 22:31, Corinna Vinschen via Cygwin wrote: > On Sep 8 12:59, Corinna Vinschen via Cygwin wrote: > > On Sep 8 06:48, Cedric Blancher via Cygwin wrote: > > > So chmod() for a FIFO inode on NFS fails. Tested with MSFT NFSv3 and > > > new builds of the NFSv4.1

Re: NFS mkfifo support in cygwin 3.5.0 Re: [ANNOUNCEMENT] cygwin 3.4.9-1

On Sep 8 12:59, Corinna Vinschen via Cygwin wrote: > On Sep 8 06:48, Cedric Blancher via Cygwin wrote: > > So chmod() for a FIFO inode on NFS fails. Tested with MSFT NFSv3 and > > new builds of the NFSv4.1 ms-nfs41-client filesystems. > > Did you actually test this with 3.

Re: ARG_MAX missing from getconf

On Sep 8 07:36, Matthew "mirage335" Hines via Cygwin wrote: > Ok, I guess that makes sense. > > My worry was some './configure' script determining that the build > environment is somehow not 'sane'. At least for the limited set of programs > that I use under cygwin, I have set up my CI to now

Re: NFS mkfifo support in cygwin 3.5.0 Re: [ANNOUNCEMENT] cygwin 3.4.9-1

On Sep 8 06:48, Cedric Blancher via Cygwin wrote: > On Thu, 7 Sept 2023 at 23:20, Martin Wege via Cygwin > wrote: > > > > On Wed, Sep 6, 2023 at 5:27 PM Corinna Vinschen via Cygwin-announce > > via Cygwin wrote: > > > > > > The following packages hav

Re: ARG_MAX missing from getconf

On Sep 8 00:14, Matthew "mirage335" Hines via Cygwin wrote: > Really hope other Cygwin packages will not be broken because 'ARG_MAX' is > now undefined in 'getconf' output. Caught this in a CI test for a rather > large shell script. > >

cygwin 3.4.9-1

The following packages have been uploaded to the Cygwin distribution: * cygwin-3.4.9-1 * cygwin-devel-3.4.9-1 * cygwin-doc-3.4.9-1 Bug Fixes - - Fix a bug introduced in cygwin 3.4.0 that switch_to_nat_pipe flag is not cleared properly when non-cygwin app is terminated in the case

[ANNOUNCEMENT] cygwin 3.4.9-1

The following packages have been uploaded to the Cygwin distribution: * cygwin-3.4.9-1 * cygwin-devel-3.4.9-1 * cygwin-doc-3.4.9-1 Bug Fixes - - Fix a bug introduced in cygwin 3.4.0 that switch_to_nat_pipe flag is not cleared properly when non-cygwin app is terminated in the case

Re: Cygwin generates syscalls for *.lnk files on filesystems with native symlink support?

On Sep 1 06:23, Cedric Blancher via Cygwin wrote: > Good morning! > > During a Cygwin 3.4.8-1.x86_64 debugging session I noticed something > odd when I looked at the network traffic generated by one of our > cluster nodes: > It seems that for each call to a tool (i.e. starting "sed" from >

Re: can't compile coreutils-9.3 any more after upgrade to cygwin-3.4.8

On Sep 1 03:28, Mark Geisert via Cygwin-apps wrote: > Hi Corinna, > > Corinna Vinschen via Cygwin-apps wrote: > > On Aug 30 20:10, Corinna Vinschen via Cygwin-apps wrote: > > > On Aug 30 12:04, Brian Inglis via Cygwin-apps wrote: > > > > On 2023-08-30 06:

Re: can't compile coreutils-9.3 any more after upgrade to cygwin-3.4.8

On Aug 30 20:10, Corinna Vinschen via Cygwin-apps wrote: > On Aug 30 12:04, Brian Inglis via Cygwin-apps wrote: > > On 2023-08-30 06:17, Corinna Vinschen via Cygwin-apps wrote: > > > On Aug 30 11:57, Corinna Vinschen via Cygwin-apps wrote: > > > > On Aug 30 11:34, Co

Re: can't compile coreutils-9.3 any more after upgrade to cygwin-3.4.8

On Aug 30 12:04, Brian Inglis via Cygwin-apps wrote: > On 2023-08-30 06:17, Corinna Vinschen via Cygwin-apps wrote: > > On Aug 30 11:57, Corinna Vinschen via Cygwin-apps wrote: > > > On Aug 30 11:34, Corinna Vinschen via Cygwin-apps wrote: > > > > #define CPU_ZE

Re: can't compile coreutils-9.3 any more after upgrade to cygwin-3.4.8

On Aug 30 11:57, Corinna Vinschen via Cygwin-apps wrote: > On Aug 30 11:34, Corinna Vinschen via Cygwin-apps wrote: > > #define CPU_ZERO_S(siz, set) __cpuset_zero_s (siz, set) > > -static __inline void > > -__cpuset_zero_s (size_t siz, cpu_set_t *set) > > -{ > &

Re: can't compile coreutils-9.3 any more after upgrade to cygwin-3.4.8

On Aug 30 11:34, Corinna Vinschen via Cygwin-apps wrote: > #define CPU_ZERO_S(siz, set) __cpuset_zero_s (siz, set) > -static __inline void > -__cpuset_zero_s (size_t siz, cpu_set_t *set) > -{ > - (void) memset (set, 0, siz); > -} > +void __cpuset_zero

Re: can't compile coreutils-9.3 any more after upgrade to cygwin-3.4.8

Hi Mark, On Aug 30 00:29, Mark Geisert via Cygwin-apps wrote: > [redirected from the main Cygwin ML] > Corinna Vinschen via Cygwin wrote: > > This is not what I meant. A simple reproducer is ideally a piece of > > C code which shows ;the problem with a minimum of code. In thi

Re: gawk core dumped on too many input values

On Aug 28 12:20, Brian Inglis via Cygwin wrote: > On 2023-08-28 05:47, Joshuah Hurst via Cygwin wrote: > > On Mon, Aug 28, 2023 at 1:08 AM Jeremy Hetzler via Cygwin > > wrote: > > > > > > On Sun, Aug 27, 2023 at 2:25 PM Ed Morton via Cygwin > > > wrote: > > > > > > > > This (original email

Re: Documenting Cygwin on NFS, no longer only exchange-medium! Re: How to fix |mkfifo()| failure if |pathname| is on NFS ? / was: Re: [EXTERNAL] Re: mkfifo: cannot set permissions of 'x.fifo': Not a d

On Aug 28 07:35, Cedric Blancher via Cygwin wrote: > On Sun, 27 Aug 2023 at 14:35, Corinna Vinschen via Cygwin > wrote: > > As for FIFOs on NFS, as I wrote, they never worked as desired on NFS. > > For kicks I tried back until Cygwin 3.3. Given this isn't a regression, >

Re: process substitution to create a virtual file doesn't work in chroot environment

On Aug 27 18:13, Cary Lewis via Cygwin wrote: > In a cygwin process that is started either from mintty or bash directly the > following: > > $ user=234 > > $ ./cat <(echo $user) > 234 > works as expected. > > But after a chroot: >From https://cygwin.com/cygwin-ug-net/highlights.html: chroot

Re: Documenting Cygwin on NFS, no longer only exchange-medium! Re: How to fix |mkfifo()| failure if |pathname| is on NFS ? / was: Re: [EXTERNAL] Re: mkfifo: cannot set permissions of 'x.fifo': Not a d

On Aug 26 19:44, Martin Wege via Cygwin wrote: > On Fri, Aug 25, 2023 at 2:19 PM Corinna Vinschen via Cygwin > wrote: > > > > On Aug 23 01:05, Roland Mainz via Cygwin wrote: > > > Note that Cygwin does not interpret the file |myfifo.fifo| as FIFO, > > >

Re: [EXTERNAL] Re: scp stalls on uploading in cygwin 3.5 current master.

On Aug 26 14:15, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: > > This thread is not about send() blocking or returning EAGAIN. This > > is about the behaviour of select(2) and poll(2). > > I was merely commenting on your note that if select() returned a socket as > writable, and

Re: How to fix |mkfifo()| failure if |pathname| is on NFS ? / was: Re: [EXTERNAL] Re: mkfifo: cannot set permissions of 'x.fifo': Not a directory

On Aug 25 23:21, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: > > it is not possible to diffentiate between Cygwin > > FIFOs and real FIFOs created from the remote side in `ls -l' > > output. > > Why would that be necessary? If it's a FIFO, it can be used as a > FIFO, regardless where

Re: How to fix |mkfifo()| failure if |pathname| is on NFS ? / was: Re: [EXTERNAL] Re: mkfifo: cannot set permissions of 'x.fifo': Not a directory

On Aug 26 13:26, Cedric Blancher via Cygwin wrote: > On Fri, 25 Aug 2023 at 14:26, Corinna Vinschen via Cygwin > wrote: > > > > On Aug 25 14:18, Corinna Vinschen via Cygwin wrote: > > > On Aug 23 01:05, Roland Mainz via Cygwin wrote: > > > > 2. Check wh

Re: can't compile coreutils-9.3 any more after upgrade to cygwin-3.4.8

On Aug 25 22:50, Mark Geisert via Cygwin wrote: > Hi Corinna, > > Corinna Vinschen via Cygwin wrote: > > On Aug 24 14:39, Mark Geisert via Cygwin wrote: > > > Denis Excoffier via Cygwin wrote: > > > > Hello, > > > > When i try t

Re: [EXTERNAL] Re: scp stalls on uploading in cygwin 3.5 current master.

On Aug 25 23:27, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: > > While select indicates that > > data can be written, it doesn't indicate how much data can be written. > > I. e., if select returns, and there's only buffer space for 10 bytes, > > and the send call tries to send 100

Re: [EXTERNAL] Re: scp stalls on uploading in cygwin 3.5 current master.

On Aug 25 14:23, Corinna Vinschen via Cygwin wrote: > On Aug 25 12:08, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: > > > I don't have an answer to this problem yet. > > > > > > Can we use send(sock, "", 0) to reenable FD_WRITE, perhaps? > >

Re: How to fix |mkfifo()| failure if |pathname| is on NFS ? / was: Re: [EXTERNAL] Re: mkfifo: cannot set permissions of 'x.fifo': Not a directory

On Aug 25 14:18, Corinna Vinschen via Cygwin wrote: > On Aug 23 01:05, Roland Mainz via Cygwin wrote: > > 2. Check whether the filesystem for the fifos path is NFS > > (cgywin.dll's |fs.fs_is_nfs()|), and then just refuse |mkfifo()| with > > |ENOSYS| (not implemented) > &

Re: [EXTERNAL] Re: scp stalls on uploading in cygwin 3.5 current master.

On Aug 25 12:08, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: > > I don't have an answer to this problem yet. > > > > Can we use send(sock, "", 0) to reenable FD_WRITE, perhaps? > > Can't it just be assumed that the socket is _always_ writeable _unless_ the > last send() failed? > In

Re: How to fix |mkfifo()| failure if |pathname| is on NFS ? / was: Re: [EXTERNAL] Re: mkfifo: cannot set permissions of 'x.fifo': Not a directory

On Aug 23 01:05, Roland Mainz via Cygwin wrote: > Note that Cygwin does not interpret the file |myfifo.fifo| as FIFO, > instead it comes back as a symlink "myfifo.fifo -> ':\0:c4:1000'". > > AFAIK there are (at least) these two options to fix the problems: > 1. Check whether the filesystem for

Re: scp stalls on uploading in cygwin 3.5 current master.

On Aug 25 17:48, Takashi Yano via Cygwin wrote: > On Thu, 24 Aug 2023 10:59:33 +0200 > Corinna Vinschen wrote: > > > I'm not sure why at all, however, the following patch seems to > > > solve the issue. > > > > > > diff --git a/winsup/cygwin/select.cc b/winsup/cygwin/select.cc > > > index

Re: Test for Windows Administrator permissions from Cygwin terminal|script?

On Aug 24 18:24, Martin Wege via Cygwin wrote: > On Sat, Aug 19, 2023 at 10:15 AM ASSI via Cygwin wrote: > > > > Martin Wege via Cygwin writes: > > > How can I find out whether the current Cygwin terminal has > > > Administrator rights? I want to safeguard our admin scripts with a > > > simple

Re: can't compile coreutils-9.3 any more after upgrade to cygwin-3.4.8

On Aug 24 14:39, Mark Geisert via Cygwin wrote: > Hi Denis, > > Thanks for the report. More below... > > Denis Excoffier via Cygwin wrote: > > Hello, > > When i try to compile coreutils-9.3 under cygwin-3.4.8 i get the following > > error messages (see below). > > There seems to be a kind of

Re: scp stalls on uploading in cygwin 3.5 current master.

On Aug 24 12:31, Takashi Yano via Cygwin wrote: > On Thu, 24 Aug 2023 06:05:02 +0900 > Takashi Yano wrote: > > Hi Corinna, > > > > After the commit dedbbd74d0a8, "scp file server:." stalls. > > I confirmed this when the "server" is a Linux machine. > > The problem does not occur if it is

Re: mkfifo: cannot set permissions of 'x.fifo': Not a directory

On Aug 21 06:49, Cedric Blancher via Cygwin wrote: > On Fri, 18 Aug 2023 at 10:35, Corinna Vinschen via Cygwin > wrote: > > > > On Aug 18 06:02, Martin Wege via Cygwin wrote: > > > On Mon, Aug 7, 2023 at 4:42 PM Martin Wege > > > wrote: > > > &g

Re: Persistent and same Cygwin session for Windows login and ssh login?

On Aug 18 12:23, Thomas Wolff via Cygwin wrote: > > > Am 18.08.2023 um 10:47 schrieb Corinna Vinschen via Cygwin: > > On Aug 17 19:30, Cedric Blancher via Cygwin wrote: > > > Good evening! > > > > > > How can I get a Cygwin session for one Windows lo

Re: Cygwin console: Different default background color when terminal runs as Admin?

On Aug 18 11:51, Martin Wege via Cygwin wrote: > On Fri, Aug 18, 2023 at 7:27 AM Jonathon Merz via Cygwin > wrote: > > > > On Thu, Aug 17, 2023 at 7:13 PM Martin Wege via Cygwin > > wrote: > > > > > Just an idea: Could the default background color of the Cygwin console > > > be changed from

Re: Cygwin openssh AllowGroups

On Aug 17 21:11, Dale Lobb via Cygwin wrote: > Is there a known issue in Cygwin's implementation of openssh in the > AllowGroups clause of sshd_config? I cannot get it to work. It should work, just as AllowUsers. Maybe you should run clinet and/or server with debugging on, to see what it

Re: Persistent and same Cygwin session for Windows login and ssh login?

On Aug 17 19:30, Cedric Blancher via Cygwin wrote: > Good evening! > > How can I get a Cygwin session for one Windows login, and get the same > Cygwin session when I log into the same Windows machine via ssh? You can't. Windows isolates sessions from each other. > Also, where does Cygwin store

Re: How does Cygwin detect MSFT NFSv3 file system? Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

On Aug 17 20:49, Martin Wege via Cygwin wrote: > On Mon, Aug 14, 2023 at 10:56 PM Corinna Vinschen via Cygwin > wrote: > > and the result is the same. Note that Cygwin supports MSFT NFSv3 but > > not CITI NFSv4.1 internally. No gurantee that Cygwin always does wha

Re: mkfifo: cannot set permissions of 'x.fifo': Not a directory

On Aug 18 06:02, Martin Wege via Cygwin wrote: > On Mon, Aug 7, 2023 at 4:42 PM Martin Wege wrote: > > > > Hello, > > > > We get a weird mkfifo failure in Cygwin on NTFS: > > > > /usr/bin/mkfifo -m 600 x.fifo > > mkfifo: cannot set permissions of 'x.fifo': Not a directory > > > > Is there a known

[ANNOUNCEMENT] cygwin 3.4.8-1

The following packages have been uploaded to the Cygwin distribution: * cygwin-3.4.8-1 * cygwin-devel-3.4.8-1 * cygwin-doc-3.4.8-1 Bug Fixes - - Make safe for c89 compilations. Addresses: https://cygwin.com/pipermail/cygwin-patches/2023q3/012308.html - Make gcc-specific code in

<    1   2   3   4   5   6   7   8   >