lrzip-0.631-1: pthread_createResource temporarily unavailable

2019-06-16 Thread David Balažic
Hi!

Using cygwin64 with latest updates, I got this error after running
lrzip (for hours):


$ lrzip -v sda.2019-apr-01.local
The following options are in effect for this COMPRESSION.
Threading is ENABLED. Number of CPUs detected: 4
Detected 17168990208 bytes ram
Compression level 7
Nice Value: 19
Show Progress
Verbose
Temporary Directory set as: /tmp/
Compression mode is: LZMA. LZO Compressibility testing enabled
Heuristically Computed Compression Window: 109 = 10900MB
Output filename is: sda.2019-apr-01.local.lrz
Warning, unable to set permissions on sda.2019-apr-01.local.lrz
File size: 128035676160
Will take 12 passes
Beginning rzip pre-processing phase
Beginning rzip pre-processing phase
Beginning rzip pre-processing phase
Beginning rzip pre-processing phase
Beginning rzip pre-processing phase
Beginning rzip pre-processing phase
Beginning rzip pre-processing phase
Beginning rzip pre-processing phase
Beginning rzip pre-processing phase
pthread_createResource temporarily unavailable
Fatal error - exiting

There is a created file with size 2640192 and name
sda.2019-apr-01.local.lrz in the same folder, after the crash.

Googling that error line find only one case:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623745
It is from year 2011 and is supposedly patched.

The $PWD is /cygdrive/z/tmp  which is a CIFS/SMB mount from a my NAS.

Regards,
David


cygcheck.out
Description: Binary data

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Are there any changes to the access control to /proc//fd/1 in cygwin 3?

2019-06-16 Thread Brian Inglis
On 2019-06-15 12:27, Till Riedel wrote:
> I have been using a very handy sudo hack, that broke lately (I think) when
> updating cygwin: https://github.com/imachug/win-sudo
> The trick is to spawn an elevated process using powershell and hook up the
> calling file descripters. I now get "write error: Bad file descriptor"
> To reproduce call:
> powershell.exe Start-Process bash  \"-c\",\"\'echo \>\>/proc/$$/fd/1 hello
> world\;sleep 10\'\"
> IMHO this used to work in former versions (print out hello world on the 
> calling
> shell). Strangely
> bash -c "echo >/proc/$$/fd/1 hello world"
> works. So my initial guess is that is has to do with the decoupling of Cygwin
> PIDs from Windows PIDs, but there were also changes in the proc file system...
> Thanks a lot in advance for any help/thoughts!

Given:
$ bash -c 'ls -dglo /dev/std* /proc/self /proc/$$ /proc/self/fd/[012]'
lrwxrwxrwx 1 15 May 14  2013 /dev/stderr -> /proc/self/fd/2
lrwxrwxrwx 1 15 May 14  2013 /dev/stdin -> /proc/self/fd/0
lrwxrwxrwx 1 15 May 14  2013 /dev/stdout -> /proc/self/fd/1
dr-xr-xr-x 3  0 Jun 16 01:37 /proc/23846
lrwxrwxrwx 1  0 Jun 16 01:37 /proc/self -> 23846
lrwxrwxrwx 1  0 Jun 16 01:37 /proc/self/fd/0 -> /dev/pty0
lrwxrwxrwx 1  0 Jun 16 01:37 /proc/self/fd/1 -> /dev/pty0
lrwxrwxrwx 1  0 Jun 16 01:37 /proc/self/fd/2 -> /dev/pty0

the following seems to work as expected:
$ powershell Start-Process bash  \"-c\",\"\'echo \>\>/dev/stdout hello
world\;sleep 10\'\"

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple