On Wed, Apr 27, 2016 at 10:23:35AM -0700, joeking wrote:
> When I try using "man", it hangs for a long time.
> From PROCMON, I see that MAN.exe is accessing
> \\man\PIPE\wkssvc - failed with BAD NETWORK PATH - about 3 seconds.
> Then
> \\share\man\ - failed with BAD NETWORK PATH - about 75 seconds
---
index.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/index.html b/index.html
index c36ec70..dfeb4d5 100755
--- a/index.html
+++ b/index.html
@@ -72,8 +72,8 @@ href="faq.html">FAQ, the User's
Guide and the mailing list
archives. If you've exhausted these resour
---
contrib.html | 6 +++---
cvs.html | 20 ++--
cygwin-ug-net/setup-net.html | 4 ++--
faq/faq.html | 2 +-
git.html | 28 ++--
lists.html | 4 ++--
navbar.html
On 4/12/2016 2:21 PM, Ken Brown wrote:
Cygwin's TeX Live 2015 collections have been updated to the latest
upstream release as test releases.
TeX Live provides a comprehensive, cross-platform TeX system. It
includes all the major TeX-related programs, macro packages, and fonts
that are free soft
The following packages have been uploaded to the Cygwin distribution:
* gtk-update-icon-cache-3.18.9-1
* gtk3-demo-3.18.9-1
* libgtk3_0-3.18.9-1
* libgtk3-devel-3.18.9-1
* libgtk3-doc-3.18.9-1
* girepository-Gtk3.0-3.18.9-1
* libgailutil3_0-3.18.9-1
* libgailutil3-devel-3.18.9-1
* libgailutil3-doc
On 4/27/16, JonY wrote:
> On 4/27/2016 08:32, Lee wrote:
>> On 4/26/16, JonY wrote:
>>> On 4/27/2016 05:08, Lee wrote:
Questions:
[.. snip ..]
>> and maybe it's a problem. I haven't tracked it down yet, but
>> GNUmakefile.in has
>> # PThreads library, if needed.
>> PTHREAD_LIB = @PTHREAD
hello,
came across this today on a fresh (2 days old) installation of cygwin x86
$ cat test.txt | head
3 [main] head (3348) C:\tools\cygwin\bin\head.exe: *** fatal error -
MapViewOfFileEx '(null)'(0x5DC), Win32 error 6. Terminating.
Segmentation fault
reading from pipes works fine if wo
On 28/04/2016 23:16, mihau wrote:
hello,
came across this today on a fresh (2 days old) installation of cygwin x86
$ cat test.txt | head
3 [main] head (3348) C:\tools\cygwin\bin\head.exe: *** fatal error
- MapViewOfFileEx '(null)'(0x5DC), Win32 error 6. Terminating.
Segmentation fault
r
Hello everybody!
First post on this mailing list, my name is Gene, I'm from Russia,
long-time Linux user, but had to use Windows as desktop for the last 8
years. Cygwin really helps me to keep my sanity! Thanks :)
I have an issue to report:
Introduction: On a UNIX system, `ln -s target link` cre
On 28.04.2016 23:23, Marco Atzeri wrote:
My cygwin is on a removable drive so your experience
is not normal.
I guess some BLODA.
thanks for the suggestion; removed everything from the path
except for the absolutely necessary, but it didn't help.
As suggested on
https://cygwin.com/problems.h
Thanks for your help.
I've attached cygcheck.out - I removed a couple of private env vars and
changed the username.
There are a lot of things in my path, so I tried shortening it to just a
bare minimum
(C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1
Greetings, Gene Pavlovsky!
> I have an issue to report:
> Introduction: On a UNIX system, `ln -s target link` creates a link
> regardless of target's existence.
> This is used in some scripts, e.g. Gentoo's `run-crons` (which I also
> use on Cygwin) uses a symlink pointing to the running process
On 04/28/2016 05:06 PM, Andrey Repin wrote:
>> Bottom line, I think the native symlink creation code should be
>> checked and a possibility should be added to create links to
>> non-existent targets, rather than the current behavior of failing.
>
> This is actually an arguable behavior, even in Li
I don't know if POSIX standard has something to say about that, but
here's a reference from GNU libc:
`man 2 symlink`:
> A symbolic link (also known as a soft link) may point to an existing
> file or to a nonexistent one; the latter case is known as a dangling link.
On 29 April 2016 at 02:
The list of errors that might be returned by symlink(2) mention target
only 3 times:
EFAULT target or linkpath points outside your accessible address space.
ENAMETOOLONG
target or linkpath was too long.
ENOENT A directory component in linkpath does not exist or is
On 29/04/2016 00:18, mihau wrote:
ZoneAlarm Personal Firewall
Can you disable it ?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscrib
On 29/04/2016 01:09, joeking wrote:
Thanks for your help.
I've attached cygcheck.out - I removed a couple of private env vars and
changed the username.
There are a lot of things in my path, so I tried shortening it to just a
bare minimum
(C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:
Greetings, Eric Blake!
> On 04/28/2016 05:06 PM, Andrey Repin wrote:
>>> Bottom line, I think the native symlink creation code should be
>>> checked and a possibility should be added to create links to
>>> non-existent targets, rather than the current behavior of failing.
>>
>> This is actually a
On 29/04/2016 03:39, b...@theworld.com wrote:
15-30 seconds to do even an ls of a small directory, seems to be
process activation.
I've spent several days on this. Cygcheck output below but W7 pro,
4GB, personal laptop, not a new CPU but otherwise seems ok and the
disk is a 480GB Sandisk SSD, f
19 matches
Mail list logo
