Re: [ANNOUNCEMENT] Update on status of make-3.82 release for cygwin

[Matthias Andree]

Am 10.08.2010, 23:00 Uhr, schrieb Christopher Faylor:


On Tue, Aug 10, 2010 at 10:51:38PM +0200, Matthias Andree wrote:

Am 10.08.2010, 19:54 Uhr, schrieb Christopher Faylor:


I wanted to let everyone know that I'm aware of the fact that make-3.82
has been released.  However, given the number of reported problems in
the make bugs mailing list, I don't plan on releasing a new version of
GNU make until the dust has settled.  That means no new version of make
for at least a month.

Also, given the ability to use more UNIX-like filenames in Cygwin  
1.7.x,

I'm contemplating not doing what I'd previously mentioned - using new
changes in GNU make to allow MS-DOS file names like "c:\foo" in
makefiles.  I'll have to investigate just how much the Windows-isms in
GNU make's code impact Cygwin make before I make a final determination.
I may just decide to reenable the --ms-dos option as it used to be in
the old days.  Or, if that's too much work, I might just turn off
special-case handling of c:\blah entirely - just like it is in
make-3.81.


How about pointing people to mingw-make? I've been using that to build
ntemacs for quite a while...


http://cygwin.com/ml/cygwin-announce/2008-02/msg6.html


Exactly - that why I'm asking why this win32/ms-dos file name re-enable  
thingy comes up

again for Cygwin's GNU make...

--
Matthias Andree

--
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: Missing APPDATA var in env of ssh sessions?

[Corinna Vinschen]

On Aug 11 00:23, Charles Wilson wrote:
> Can ssh (or is it cygwin1.dll?) ensure that the user's APPDATA variable
> is populated, since it appears to be a pretty important var for Windows
> Vista+?

The child process started by sshd inherits its minimal environment from
its sshd server parent process.  The sshd server is running under
another account and so has another set of environment variables.  The
setuid() call does not change the environment.  There's no mechanism to
fetch a user-specific environment other than the officially supported
mechanisms as described in `man sshd' and `man sshd_config':

In `man sshd' see the LOGIN PROCESS and SSHRC sections, as well as the
AUTHORIZED_KEYS FILE FORMAT section.

In `man sshd_config' see the descriptions for AcceptEnv and
PermitUserEnvironment.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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: Cygwin DLL 1.7.5-1 would not interfere with Symantec anti virus?

[Corinna Vinschen]

On Aug 10 21:26, lala_23...@yahoo.com wrote:
> Hello. One of the issues fixed under the New Cygwin DLL 1.7.5-1
> release is the memory leak. Does this mean that we wont have any
> problems ruuning anti virus software like Symantec anymore? 

What is "the" memory leak?  What has a memory leak to do with
interference by BLODAs?


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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: 1.7.5: Occasional failure of CreatePipe or signal handing due to thread-unsafe code in cwdstuff::set

[Corinna Vinschen]

On Aug 10 21:53, John Carey wrote:
> On Aug 10 13:44 +0200 Corinna Vinschen wrote:
> >   chdir ("/");
> >   h = CreateFile ("foobar", ...);
> >   if (h == INVALID_HANDLE_VALUE) printf ("%lu\n", GetLastError());
> 
> Thanks for the test case for the CreateFile() problem; I used it to
> create the following test, in which Windows 7 CreateFile() fails with
> ERROR_INVALID_HANDLE even when using a stock Cygwin 1.7.5 DLL:
> [...]

Thanks for the test case.

> The PEB lock in cwdstuff::set() can only prevent the race if other
> threads always hold the PEB lock while invoking system calls that
> allocate handles.  CreateFile() is pretty big, so I might have missed
> it, but I did not see CreateFile() holding the PEB lock while actually
> creating the new file handle.

No, it doesn't have to.  It only needs the PEB lock when accessing
the cwd in the PEB.  But ...

>   Instead, after actually creating the
> new file handle, it called _rtlreleaserelativen...@4 on
> a reference-counted object that holds a copy of the current
> directory handle (see below for more about such reference-counted
> current directory objects).

... if that's correct it seems that the cwd from the PEB isn't even used
in Vista++.  That explains why just exchanging the handle value in
cwdstuff::set() only works fine in 2K3 and earlier systems.  Bummer.
I assume the idea was to speed up CreateFile by getting rid of a lock
per call.

> Now, where is Windows stuffing the extra copy of the directory handle?
> In those reference-counted heap-allocated directory objects.  Stepping
> through the machine code under Windows 7 I see SetCurrentDirectory()
> updating a global pointer ("ntdll!RtlpCurDirRef") to one such object,
> under the protection of a critical section ("ntdll!FastPebLock").
> Despite mentioning "Peb" in the name, neither global's address is
> computed using "FS:".  The global pointer points to a heap-allocated
> block that starts with a reference count followed by a copy of the
> directory handle value, and apparently includes other data as well.
> SetCurrentDirectory() swaps in a new such block, and decrements the
> counter on the old block, and if that reaches 0, closes the handle.
> Anyway, this block appears to be where the old current directory
> handle value persists past the changes made by cwdstuff::set().

...and that handle is used in subsequent calls and potentially is a
handle to another object in the meantime.

I do basically agree with cgf that it's your own problem if you use
Win32 calls in your Cygwin app.  OTOH, I see that this can trip up
potential handle problems in the DLL itself.

Unfortunately that means there's no Win32-safe way to set a new
directory handle as cwd in Vista and later anymore.  Since there's no
official API to set the cwd using a directory handle, there's no way to
set the Win32 cwd to a directory with restricted permissions.
This *is* frustrating.

I'll look into another solution.  Probably we will have to call
SetCurrentDirectory again and ignore any error.  I don't accept the
aforementioned restriction for POSIX calls.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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: 1.7.5: Occasional failure of CreatePipe or signal handing due to thread-unsafe code in cwdstuff::set

[Andrey Repin]

Greetings, Al Slater!

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1

> On 10/08/2010 09:57, Andrey Repin wrote:
>> Greetings, John Carey!
>> 
>>> After a call to SetCurrentDirectory(), I have seen occasional (< 5%)
>>> failures of CreatePipe() with code ERROR_INVALID_HANDLE.  I have also seen
>>> failure of Cygwin signal handling because the signal handling pipe has
>>> mysteriously closed. 
>> 
>> Seems like it was discussed a short while ago.
>> mid:008101cb3597$a75069f0$f5f13d...@gmail.com

> Out of interest, what is that strange email address above supposed to
> refer to?

mid - message ID.
If you have normal mail/news reader, and you have this message in your local
database, it will be a link and clicking it will bring you to that message.


--
WBR,
 Andrey Repin (anrdae...@freemail.ru) 11.08.2010, <13:29>

Sorry for my terrible english...


--
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: 1.7.5: Occasional failure of CreatePipe or signal handing due to thread-unsafe code in cwdstuff::set

[Daniel Colascione]

On 8/10/10 10:44 PM, Christopher Faylor wrote:
> On Tue, Aug 10, 2010 at 09:53:46PM +, John Carey wrote:
>> Thanks for the test case for the CreateFile() problem; I used it to
>> create the following test, in which Windows 7 CreateFile() fails with
>> ERROR_INVALID_HANDLE even when using a stock Cygwin 1.7.5 DLL:
> 
> As Corinna said:  If you are mixing Windows calls with cygwin calls you
> are far into unsupported territory.  Cygwin isn't designed to let you
> seamlessly intermix things like pthreads/signals and the Windows API
> functions.

Then it seems the website needs to be updated. One of the major selling
points of Cygwin, as it were, is the ability to interact with the
Windows API world as well as the POSIX one: "Because processes run under
the standard Win32 subsystem, they can access both the UNIX
compatibility calls provided by Cygwin as well as any of the Win32 API
calls. This gives the programmer complete flexibility in designing the
structure of their program in terms of the APIs used. For example, they
could write a Win32-specific GUI using Win32 API calls on top of a UNIX
back-end that uses Cygwin."

I can understand requiring that users not deliberately create
inconsistencies between Cygwin data structures and those of Windows (and
I can understand throwing people who do that to the wolves), but
CreateFile is a fundamental system facility that should always work,
even in a Cygwin process.

--
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: Incomplete installation of subversion

[Andy Koppe]

On 10 August 2010 12:59, Andy Koppe wrote:
> On 10 August 2010 12:41, David Balažic wrote:
>> I have a reasonably up to date cygwin installation (did an update a
>> week ago or so).
>> Today I run the latest setup (v2.708). In Pending I saw a few libX
>> packages and minttty 0.8.1.
>>
>> Then I selected subversion for install.
>> On "Next" I got a dialog saying that subversion depended on additional 
>> packages.
>> I clicked... I don't really remember what, I guess it was OK or Yes.
>>
>> Then it installed subversion and the updates.
>>
>> But when I started mintty and entered svn, I got this:
>>
>> $ svn
>> /usr/bin/svn.exe: error while loading shared libraries: ?: cannot open
>> shared object file: No such file or directory
>>
>> I started Setup again, and now under Pending I see:
>>  - wouldn't it be wonderful to be able to copy paste text from dialogs?
>>  - crypt
>>  - libgdm4
>>  - libopenldap2_3_0
>>  - libopenssl098
>>  - libpq5
>>  - libproxy0
>>  - minires
>>
>> So what did I do wrong?
>
> Nothing. It's a bug in the resolver behind the "Unmet dependencies"
> page: it doesn't add indirect dependencies. This is fixed in CVS, to
> be rolled out soon.

Setup.exe 2.712 with a fix for this and a few additional tweaks to the
"Unmet dependencies" page has been uploaded to http://cygwin.com.

Andy

--
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: 1.7.5: Occasional failure of CreatePipe or signal handing due to thread-unsafe code in cwdstuff::set

[Corinna Vinschen]

On Aug 11 04:05, Daniel Colascione wrote:
> On 8/10/10 10:44 PM, Christopher Faylor wrote:
> > On Tue, Aug 10, 2010 at 09:53:46PM +, John Carey wrote:
> >> Thanks for the test case for the CreateFile() problem; I used it to
> >> create the following test, in which Windows 7 CreateFile() fails with
> >> ERROR_INVALID_HANDLE even when using a stock Cygwin 1.7.5 DLL:
> > 
> > As Corinna said:  If you are mixing Windows calls with cygwin calls you
> > are far into unsupported territory.  Cygwin isn't designed to let you
> > seamlessly intermix things like pthreads/signals and the Windows API
> > functions.
> 
> Then it seems the website needs to be updated. One of the major selling
> points of Cygwin, as it were, is the ability to interact with the
> Windows API world as well as the POSIX one: "Because processes run under
> the standard Win32 subsystem, they can access both the UNIX
> compatibility calls provided by Cygwin as well as any of the Win32 API
> calls. This gives the programmer complete flexibility in designing the
> structure of their program in terms of the APIs used. For example, they
> could write a Win32-specific GUI using Win32 API calls on top of a UNIX
> back-end that uses Cygwin."
> 
> I can understand requiring that users not deliberately create
> inconsistencies between Cygwin data structures and those of Windows (and
> I can understand throwing people who do that to the wolves), but
> CreateFile is a fundamental system facility that should always work,
> even in a Cygwin process.

There's a problem, and the current problem is a typical representation
for this, so let's stick to this example.

In Cygwin it is possible to chdir to a directory to which you can't cd
using the SetCurrentDirectory call.  If you're an administrator, you
have BACKUP_NAME privileges.  So you can access files in directories
which don't give you this permission usually, just like a root user on
Linux.

Unfortunately the SetCurrentDirectory call doesn't support this.  It
only takes a Win32 pathname which is subsequently opened without providing
the FILE_FLAG_BACKUP_SEMANTICS flag.  So, while you can *open* files in
such a dir using the FILE_FLAG_BACKUP_SEMANTICS flag, you can't set your
CWD to it when using the Win32 API.

Another exmaple:  Windows supports path of up to 32768 bytes.  However,
the Win32 CWD can have a maximum length of 259 chars.  Even when using
the UNICODE API!

None of these restriction exist for Cygwin applications *iff* they use
the POSIX API.

So, what if a Cygwin application chdir'ed into such a directory
successfully?  If I change back Cygwin to use SetCurrentDirectory
to keep the Win32 API in sync, the call will fail in the first example,
while the second example is never supported in the Win32 API.

In effect, the POSIX API CWD is now a different one than the Win32 API
CWD.

So, what does sticking to Win32 compatibility mean?

Does that mean we have still the right to make the POSIX API as good as
possible, thus risking that CreateFile with a relative filename fails or
accesses another file than the POSIX open call?

Or does that mean we have to revert all these changes since we don't
have the right to provide better or more functionality in the POSIX API
if it potentially breaks the Win32 API?


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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: Missing APPDATA var in env of ssh sessions?

[Charles Wilson]

On 8/11/2010 4:01 AM, Corinna Vinschen wrote:
> On Aug 11 00:23, Charles Wilson wrote:
>> Can ssh (or is it cygwin1.dll?) ensure that the user's APPDATA variable
>> is populated, since it appears to be a pretty important var for Windows
>> Vista+?
>
> In `man sshd' see the LOGIN PROCESS and SSHRC sections, as well as the
> AUTHORIZED_KEYS FILE FORMAT section.
> 
> In `man sshd_config' see the descriptions for AcceptEnv and
> PermitUserEnvironment.

Thanks. I was able to get the desired behavior by;

1) adding 'PermitUserEnvironment yes' to /etc/sshd_config
2) restarting sshd, and
3) Adding a new file, ~/.ssh/environment, with the following content
APPDATA=C:\Users\me\AppData\Roaming

Then, logging in via ssh, the new environment has the correct value, and
"mingw-get" doesn't litter my CWD with %APPDATA% directories.

I was thinking this facility might be made the default via updates to
ssh-user-config and ssh-host-config, but 'PermitUserEnvironment' carries
a pretty severe warning in 'man sshd_config', so probably not.

Those affected will probably find this thread, and the solution, for
themselves.

--
Chuck

--
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: Missing APPDATA var in env of ssh sessions?

[Corinna Vinschen]

On Aug 11 08:08, Charles Wilson wrote:
> On 8/11/2010 4:01 AM, Corinna Vinschen wrote:
> > On Aug 11 00:23, Charles Wilson wrote:
> >> Can ssh (or is it cygwin1.dll?) ensure that the user's APPDATA variable
> >> is populated, since it appears to be a pretty important var for Windows
> >> Vista+?
> >
> > In `man sshd' see the LOGIN PROCESS and SSHRC sections, as well as the
> > AUTHORIZED_KEYS FILE FORMAT section.
> > 
> > In `man sshd_config' see the descriptions for AcceptEnv and
> > PermitUserEnvironment.
> 
> Thanks. I was able to get the desired behavior by;
> 
> 1) adding 'PermitUserEnvironment yes' to /etc/sshd_config
> 2) restarting sshd, and
> 3) Adding a new file, ~/.ssh/environment, with the following content
> APPDATA=C:\Users\me\AppData\Roaming
j 
> Then, logging in via ssh, the new environment has the correct value, and
> "mingw-get" doesn't litter my CWD with %APPDATA% directories.
> 
> I was thinking this facility might be made the default via updates to
> ssh-user-config and ssh-host-config, but 'PermitUserEnvironment' carries
> a pretty severe warning in 'man sshd_config', so probably not.
> 
> Those affected will probably find this thread, and the solution, for
> themselves.

Indeed, I rather stick to the default options as given in the upstream
release.

Btw., what you can do as well is to set APPDATA in a shell profile,
for instance in /etc/profile.d:

  _sid=$(grep "^$USER:" /etc/passwd | sed -e 
's/[^:]*:[^:]*:[^:]*:[^:]*:[^:]*,\(S-1-5-[^:]*\):.*/\1/')
  _prof=$(cat /proc/registry/HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows\ 
NT/CurrentVersion/ProfileList/${_sid}/ProfileImagePath)
  export APPDATA="${_prof}\\AppData\\Roaming"
  unset sid
  unset prof


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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: Windows Server 2008 64-bit setup.exe/bash problem - Amazon Cloud

[Dave Cottlehuber]

On 7/15/2010 11:44 AM, Ernest Mueller wrote:

Michael, did you ever find a fix for this?  I had to give up on cygwin on
the Amazon 64-bit and instead cobbled together freesshd and random
freewares.


Larry or others - what's the "right way" to report this as a bug?  I think
working on newer 64-bit OSes is pretty important...  And it should be
trivial to reproduce since the Amazon instances are publicly available;
nobody has to actually buy them expensive licenses...


Reporting this issue on the list is the right way to report the bug.

--
Larry Hall  http://www.rfk.com


I have found 1 more piece of the puzzle - unfortunately not a complete
solution but it does seem to helpa. Any further ideas?

http://support.microsoft.com/kb/956607
http://dch.posterous.com/cygwin-dumps-core-on-windows-2008-r1sp2-on-ec

I'd appreciate a cc with any further info,  as I am not a list subscriber.

cheers
Dave

--
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: Vertical split in GNU screen

[f...@neotek.fr]

Thanks a lot for your quick answer! I will be pleased if you could
post the version of Screen with vsplit patch  as a test release
because i didn't try to compile for cygwin yet!
I will try it and give my feedback! I'm on winxp sp3!
Rgds,
Florent..

2010/8/6 Andrew Schulman :
>> Hi, i'm new with mailing-lists use!
>> i'd like to re-talk about a feature with cygwin screen! How can we add
>> the marvellous "Vertical split in GNU screen" with cygwin?
>> I know there were a talk about that between Jeenu V > dot com> and Andrew Schulman > dot gov> the 19 Apr 2010!
>> Thanks in advance for somebody answer!
>> If i'm not at the right place to talk about this or if i don't use
>> this list in the good way, please don't shout at me, just show me!
>> Florent LOTTIN
>
> Hi Florent.  There is a patch that's been available for a while, that adds
> vertical split support to screen.  I believe that Debian, Ubuntu, and
> probably others already incorporate it into their official screen packages.
>
> I remember the exchange with Jeenu, and after that I did go get the patch,
> build screen with it for Cygwin, and try it out.  What I found, if I
> remember right, is that I saw a lot of what I considered strange behavior,
> and very little documentation or help about how the vertical split feature
> is supposed to work.  It didn't seem to me to be working very well, so I
> put it aside.
>
> If people would like to try out the patched version, I can post it as a
> test release.  Maybe you can tell me if the vertical split feature is
> working the way it's supposed to.
>
> Andrew.
>
>
> --
> 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
>
>

--
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: [ANNOUNCEMENT] Update on status of make-3.82 release for cygwin

[Christopher Faylor]

On Wed, Aug 11, 2010 at 09:32:13AM +0200, Matthias Andree wrote:
>Am 10.08.2010, 23:00 Uhr, schrieb Christopher Faylor:
>
>> On Tue, Aug 10, 2010 at 10:51:38PM +0200, Matthias Andree wrote:
>>> Am 10.08.2010, 19:54 Uhr, schrieb Christopher Faylor:
>>>
 I wanted to let everyone know that I'm aware of the fact that make-3.82
 has been released.  However, given the number of reported problems in
 the make bugs mailing list, I don't plan on releasing a new version of
 GNU make until the dust has settled.  That means no new version of make
 for at least a month.

 Also, given the ability to use more UNIX-like filenames in Cygwin  
 1.7.x,
 I'm contemplating not doing what I'd previously mentioned - using new
 changes in GNU make to allow MS-DOS file names like "c:\foo" in
 makefiles.  I'll have to investigate just how much the Windows-isms in
 GNU make's code impact Cygwin make before I make a final determination.
 I may just decide to reenable the --ms-dos option as it used to be in
 the old days.  Or, if that's too much work, I might just turn off
 special-case handling of c:\blah entirely - just like it is in
 make-3.81.
>>>
>>> How about pointing people to mingw-make? I've been using that to build
>>> ntemacs for quite a while...
>>
>> http://cygwin.com/ml/cygwin-announce/2008-02/msg6.html
>
>Exactly - that why I'm asking why this win32/ms-dos file name re-enable  
>thingy comes up
>again for Cygwin's GNU make...

"I'm contemplating not doing what I'd previously mentioned"
   ^^^

I had said that I'd reenable it if things changed in make.  I've changed
my mind so I was letting people know.

cgf

--
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

OpenSSH: 5791 [main] sshd 9288! spawn_guts: CreateDesktop failed, Win32 error 8

[Carsten . Porzler]

Dear Cygwin community,

unfortunately we got on some of our Windows 2003 servers this error 
message while logging on by using OpenSSH

   5791 [main] sshd 9288! spawn_guts: CreateDesktop failed, Win32 error 8

This error message occurs after the server has been rebooted.

If log on once at the Windows console as a user with local admin 
privileges, also the SSH logon works again.

We are using Cygwin CYGWIN_NT-5.2 d20of001 1.7.0(0.200/5/3) 2009-02-20 
17:20 i686 Cygwin and OpenSSH 5.1.

Does anybody know the reason for this failure?

Thanks a lot in advance and best regards

Carsten Porzler


--
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: 1.7.5: Occasional failure of CreatePipe or signal handing due to thread-unsafe code in cwdstuff::set

[Christopher Faylor]

On Wed, Aug 11, 2010 at 04:05:32AM -0700, Daniel Colascione wrote:
>On 8/10/10 10:44 PM, Christopher Faylor wrote:
>> On Tue, Aug 10, 2010 at 09:53:46PM +, John Carey wrote:
>>> Thanks for the test case for the CreateFile() problem; I used it to
>>> create the following test, in which Windows 7 CreateFile() fails with
>>> ERROR_INVALID_HANDLE even when using a stock Cygwin 1.7.5 DLL:
>> 
>> As Corinna said:  If you are mixing Windows calls with cygwin calls you
>> are far into unsupported territory.  Cygwin isn't designed to let you
>> seamlessly intermix things like pthreads/signals and the Windows API
>> functions.
>
>Then it seems the website needs to be updated. One of the major selling
>points of Cygwin, as it were, is the ability to interact with the
>Windows API world as well as the POSIX one: "Because processes run under
>the standard Win32 subsystem, they can access both the UNIX
>compatibility calls provided by Cygwin as well as any of the Win32 API
>calls. This gives the programmer complete flexibility in designing the
>structure of their program in terms of the APIs used. For example, they
>could write a Win32-specific GUI using Win32 API calls on top of a UNIX
>back-end that uses Cygwin."

I've removed that paragraph.  Thanks for the heads up.

cgf

--
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

Postinstall script errors

[Jeremy Ramer]

I recently upgraded from cygwin 1.5 to 1.7. At the end of the install
there were errors with some of the postinstall scripts.  From the
setup.full.log:

2010/08/11 08:39:53 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/bash.sh
ln: creating symbolic link `/dev/stdin': File exists
2010/08/11 08:39:54 abnormal exit: exit code=1
2010/08/11 08:39:54 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/passwd-grp.sh
2010/08/11 08:39:55 abnormal exit: exit code=1


I tried manually running the scripts with mixed results

$ bash --norc --noprofile /etc/postinstall/bash.sh ; echo $?
0

$ bash --norc --noprofile /etc/postinstall/passwd-grp.sh ; echo $?
1

I tired manually running the commands inside passwd-grp.sh and they
all return 0. So I'm not sure what exactly is failing.  Is there
anything I should do to investigate?

Thanks!
Jeremy

--
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: OpenSSH: 5791 [main] sshd 9288! spawn_guts: CreateDesktop failed, Win32 error 8

[Larry Hall (Cygwin)]

On 8/11/2010 10:14 AM, carsten.porz...@spb.de wrote:

Dear Cygwin community,

unfortunately we got on some of our Windows 2003 servers this error
message while logging on by using OpenSSH

5791 [main] sshd 9288! spawn_guts: CreateDesktop failed, Win32 error 8

This error message occurs after the server has been rebooted.

If log on once at the Windows console as a user with local admin
privileges, also the SSH logon works again.

We are using Cygwin CYGWIN_NT-5.2 d20of001 1.7.0(0.200/5/3) 2009-02-20
17:20 i686 Cygwin and OpenSSH 5.1.

Does anybody know the reason for this failure?


It's really not clear to me from the above whether you're dealing with
domain users in the failing case but if so, please read the following
FAQ:



--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.

Q: Are you sure?

A: Because it reverses the logical flow of conversation.

Q: Why is top posting annoying in email?


--
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

Cannot run psql under Cygwin

[Clement, Sebastien]

When I try to run psql (eg. psql -U myusername -d mydb) from Cygwin, it freezes.
When I run it from the DOS console, it works fine.

Here are the versions on my system:
Windows XP Pro 2002, Service Pack 3
Cygwin: CYGWIN_NT-5.1 W-QUE-A103212 1.7.5(0.225/5/3) 2010-04-12 19:07 i686 
Cygwin
PostgreSQL: 8.4.4
No version of PostgreSQL was installed under Cygwin.

Sébastien Clément


--
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: Cannot run psql under Cygwin

[Larry Hall (Cygwin)]

On 8/11/2010 11:57 AM, Clement, Sebastien wrote:

When I try to run psql (eg. psql -U myusername -d mydb) from Cygwin, it freezes.
When I run it from the DOS console, it works fine.


In that case, you need to run Cygwin's bash from a console (i.e. use
'cygwin.bat' as provided by 'setup.exe') and run 'psql' from there.
See the 'tty' option for the CYGWIN environment variable in the Users
Guide for more details:



--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.

Q: Are you sure?

A: Because it reverses the logical flow of conversation.

Q: Why is top posting annoying in email?


--
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

vi and vim

[Dave Robison]

 Hello,

At the risk of bringing down a cascade of derision, is there any way to 
use vi instead of vim in cygwin?


I really prefer vi, but I can't seem to find a binary for it which isn't 
linked to one iteration or another of vim.


If not, c'est la vie.

Thanks for your time,

Dave



--
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: Cannot run psql under Cygwin

[Clement, Sebastien]

Okay, many thanks Larry.

I forgot to mention I was using the MinTTY console.
It works when I use the regular Cygwin console.

I found that:
http://cygwin.com/ml/cygwin/2009-10/msg00330.html


Sébastien
--



On 8/11/2010 11:57 AM, Clement, Sebastien wrote:

When I try to run psql (eg. psql -U myusername -d mydb) from Cygwin, it 
freezes.
When I run it from the DOS console, it works fine.


In that case, you need to run Cygwin's bash from a console (i.e. use
'cygwin.bat' as provided by 'setup.exe') and run 'psql' from there.
See the 'tty' option for the CYGWIN environment variable in the Users
Guide for more details:




--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

--
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: vi and vim

[Larry Hall (Cygwin)]

On 8/11/2010 12:22 PM, Dave Robison wrote:

Hello,

At the risk of bringing down a cascade of derision, is there any way to
use vi instead of vim in cygwin?

I really prefer vi, but I can't seem to find a binary for it which isn't
linked to one iteration or another of vim.

If not, c'est la vie.


Cygwin provides the vim package, which creates a link to 'vim-nox.exe'
called 'vi'.  Unless you set 'nocompatible' in your ~/.vimrc, you will get
a vi-compatible version of vim.  vim is the only package in the Cygwin
distribution providing 'vi'.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.

Q: Are you sure?

A: Because it reverses the logical flow of conversation.

Q: Why is top posting annoying in email?


--
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: Cannot run psql under Cygwin

[Steve Holden]

This is running in a mintty console on a fairly recent (updated four
days ago) Cygwin load and the standard Windows PostgreSQL server:

shol...@lifeboy ~/Projects/PytDj/Pyteach/templates/training
$ psql -h localhost -p 5432 -U django PyTeach
Password for user django:
Welcome to psql 8.2.11 (server 8.3.5), the PostgreSQL interactive terminal.

Type:  \copyright for distribution terms
   \h for help with SQL commands
   \? for help with psql commands
   \g or terminate with semicolon to execute query
   \q to quit

WARNING:  You are connected to a server with major version 8.3,
but your psql client is major version 8.2.  Some backslash commands,
such as \d, might not work properly.

PyTeach=> select * from city;
 id |  ctyname
+---
  2 | Washington, DC
  6 | New York, NY
  7 | London, England
  8 | Boston, MA
  9 | Chicago, IL
 10 | Atlanta, GA
 11 | Los Angeles, CA
 12 | San Francisco, CA
(8 rows)

PyTeach=> \q

shol...@lifeboy ~/Projects/PytDj/Pyteach/templates/training
$ which psql
/usr/bin/psql

Had you considered using the Cygwin psql rather than the Windows one?

regards
 Steve

On 8/11/2010 12:23 PM, Clement, Sebastien wrote:
> Okay, many thanks Larry.
> 
> I forgot to mention I was using the MinTTY console.
> It works when I use the regular Cygwin console.
> 
> I found that:
> http://cygwin.com/ml/cygwin/2009-10/msg00330.html
> 
> 
> Sébastien
> --
> 
> 
> 
> On 8/11/2010 11:57 AM, Clement, Sebastien wrote:
> 
> When I try to run psql (eg. psql -U myusername -d mydb) from Cygwin, it 
> freezes.
> When I run it from the DOS console, it works fine.
> 
> 
> In that case, you need to run Cygwin's bash from a console (i.e. use
> 'cygwin.bat' as provided by 'setup.exe') and run 'psql' from there.
> See the 'tty' option for the CYGWIN environment variable in the Users
> Guide for more details:
> 
> 
> 
> 
> --
> Larry Hall  http://www.rfk.com
> RFK Partners, Inc.  (508) 893-9779 - RFK Office
> 216 Dalton Rd.  (508) 893-9889 - FAX
> Holliston, MA 01746
> 


-- 
Steve Holden   +1 571 484 6266   +1 800 494 3119
DjangoCon US September 7-9, 2010http://djangocon.us/
See Python Video!   http://python.mirocommunity.org/
Holden Web LLC http://www.holdenweb.com/


--
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

tar permission errors when copying directories to a server

[Mirko Vukovic]

Hello,

I use tar to backup my files to a server using a command

>tar  cf - . --exclude-from=./.backup-exclude | (cd "$dest_dir"; tar xvf -) 
> > "$log_file"

After finally upgrading to 1.7, I started getting the following errors:

tar: ./dir-name1: Cannot change mode to rwx-w--w-: Permission denied
tar: ./dir-name2: Cannot change mode to rwx-w--w-: Permission denied
tar: .: Cannot change mode to rwxrw-rw-: Permission denied
tar: Exiting with failure status due to previous errors
tar exited with error status 1 on  Wed Aug 11 12:56:39 EDT 2010

Irrespective of these errors, tar does copy all the files.  The
problem is that I use the exit status to check whether the backup
succeeded or not and whether to reset the time-stamp file.  So, the
error status is important to me.

I tried the same script to copy files from one location to another on
my machine, and it works without errors.

I am guessing that the problem has something to do with permissions on
the server.  How would I go about fixing those?

Thank you,

Mirko

--
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: 1.7.5: Occasional failure of CreatePipe or signal handing due to thread-unsafe code in cwdstuff::set

[John Carey]

On Aug 11 01:49 Corinna Vinschen wrote:
> On Aug 10 21:53, John Carey wrote:
> > Now, where is Windows stuffing the extra copy of the directory handle?
> > In those reference-counted heap-allocated directory objects.  Stepping
> > through the machine code under Windows 7 I see SetCurrentDirectory()
> > updating a global pointer ("ntdll!RtlpCurDirRef") to one such object,
> > under the protection of a critical section ("ntdll!FastPebLock").
> > Despite mentioning "Peb" in the name, neither global's address is
> > computed using "FS:".  The global pointer points to a heap-allocated
> > block that starts with a reference count followed by a copy of the
> > directory handle value, and apparently includes other data as well.
> > SetCurrentDirectory() swaps in a new such block, and decrements the
> > counter on the old block, and if that reaches 0, closes the handle.
> > Anyway, this block appears to be where the old current directory
> > handle value persists past the changes made by cwdstuff::set().
> 
> ...and that handle is used in subsequent calls and potentially is a
> handle to another object in the meantime.
> 
> I do basically agree with cgf that it's your own problem if you use
> Win32 calls in your Cygwin app.  OTOH, I see that this can trip up
> potential handle problems in the DLL itself.
> 
> Unfortunately that means there's no Win32-safe way to set a new
> directory handle as cwd in Vista and later anymore.  Since there's no
> official API to set the cwd using a directory handle, there's no way to
> set the Win32 cwd to a directory with restricted permissions.
> This *is* frustrating.
> 
> I'll look into another solution.  Probably we will have to call
> SetCurrentDirectory again and ignore any error.  I don't accept the
> aforementioned restriction for POSIX calls.

So is your idea that if SetCurrentDirectory() fails because
of path length or permissions, then Cygwin would just accept
the failure and keep an internal record the
POSIX current working directory and use that for all
Cygwin calls, not the Win32 notion of current directory?

-- John

--
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: Incomplete installation of subversion

[Andrey Repin]

Greetings, Andy Koppe!

> Setup.exe 2.712 with a fix for this and a few additional tweaks to the
> "Unmet dependencies" page has been uploaded to http://cygwin.com.

Can't download it - server not sending file size, causing download to abort.


--
WBR,
 Andrey Repin (anrdae...@freemail.ru) 12.08.2010, <0:51>

Sorry for my terrible english...


--
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: Incomplete installation of subversion

[Larry Hall (Cygwin)]

On 8/11/2010 4:51 PM, Andrey Repin wrote:

Greetings, Andy Koppe!


Setup.exe 2.712 with a fix for this and a few additional tweaks to the
"Unmet dependencies" page has been uploaded to http://cygwin.com.


Can't download it - server not sending file size, causing download to abort.


Works fine for me from here.  

Sounds like something is getting in the way.  Proxy?

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.

Q: Are you sure?

A: Because it reverses the logical flow of conversation.

Q: Why is top posting annoying in email?


--
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

abnormal exit codes

[Stephen Dewey]

Hi, I am trying to install Cygwin (latest version, 1.7.5-1) on a
Windows XP Professional computer, and I keep getting errors that
certain scripts exited with abnormal codes. Specifically:

Package: libglade2.0_0
 libglade2.0.sh exit code 2
Package: mined
 mined.sh exit code 1
Package: No package
 libglade2.0.sh exit code 2
 mined.sh exit code 1

I have checked and these are selected during the Cygwin install
process. I have made sure that all dependencies are selected (or at
least, the ones detected by the Cygwin installer). Generally I'm doing
the basic installation but adding the Perl, Python, Database, Shell,
and Net packages (roughly).

These packages aren't crucial to what I'm doing, but I'd feel better
about a clean install. Unfortunately, setup.log doesn't tell me
anything new, just (partially):

2010/08/11 18:00:22 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/libncurses-devel.sh
2010/08/11 18:00:23 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/libglade2.0.sh
2010/08/11 18:00:23 abnormal exit: exit code=2
2010/08/11 18:00:23 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/gq.sh
2010/08/11 18:00:26 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/grepmail.sh
2010/08/11 18:00:26 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/gv.sh
2010/08/11 18:00:26 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/vim.sh
2010/08/11 18:00:26 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/gvim.sh
2010/08/11 18:00:29 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/inetutils.sh
2010/08/11 18:00:44 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/irssi.sh
2010/08/11 18:00:45 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/joe.sh
2010/08/11 18:00:45 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/lftp.sh
2010/08/11 18:00:45 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/libdb2-devel.sh
2010/08/11 18:00:45 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/libdb3.1-devel.sh
2010/08/11 18:00:46 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/libdb3.3-devel.sh
2010/08/11 18:00:46 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/libdb4.0-devel.sh
2010/08/11 18:00:46 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/libdb4.1-devel.sh
2010/08/11 18:00:46 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/libdb4.2-devel.sh
2010/08/11 18:00:46 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/libdb4.3-devel.sh
2010/08/11 18:00:47 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/libdb4.4-devel.sh
2010/08/11 18:00:47 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/libdb4.5-devel.sh
2010/08/11 18:00:47 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/post-texmf.sh
2010/08/11 18:02:51 can't run /etc/postinstall/post-texmf.sh: No such file
2010/08/11 18:02:51 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/lyx.sh/lyx.sh
2010/08/11 18:02:51 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/maradns.sh
2010/08/11 18:02:51 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/mined.sh
2010/08/11 18:02:51 abnormal exit: exit code=1
2010/08/11 18:02:51 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/mintty.sh
2010/08/11 18:02:52 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/wget.sh
2010/08/11 18:02:52 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/openldap.sh
2010/08/11 18:02:52 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/pdksh.sh
2010/08/11 18:02:52 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/proftpd.sh
2010/08/11 18:02:53 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/rsh.sh
2010/08/11 18:02:53 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/rsnapshot.sh
2010/08/11 18:02:53 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/rxvt.sh
2010/08/11 18:02:54 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/rxvt-unicode-common.sh
2010/08/11 18:02:55 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/rxvt-unicode-X.sh
2010/08/11 18:02:55 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/sendxmpp.sh
2010/08/11 18:02:55 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/tcp_wrappers.sh
2010/08/11 18:02:56 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/tcsh.sh
2010/08/11 18:02:56 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/ted.sh
2010/08/11 18:02:56 can't run /etc/postinstall/post-texmf.sh: No such file
2010/08/11 18:02:56 running: C:\cygwin\bin\bash.exe --norc --noprofile
/etc/postinstall/tirc.sh
2010/08/11 18:02:56

CygWin Security & Performance Issues

[David Law]

 Hello List,

about 18 months ago we recommended cygwin as a unix-like
environment for a Windows 2003 Server to our Admin.

This was turned down on the grounds that it did not satisfy
the security requirements of our organisation. (unfortunately
I don't know the details as I wasn't involved in the process)

Instead, the "Subsystem for Unix-based Applications" was chosen.

I am now trying to port a fairly simple shell script to SUA
and find massive performance problems: under cygwin the script
runs for about 20 minutes on my notebook, but under SUA it takes
about 2 days on our Zillion-core 2003 Server!!

Firstly, I was wondering if SUA maybe has a reputation for
bad performance, or could it maybe be the architecture of
desktop contra server pc's?
Would you expect better performance from cygwin?

Secondly, how do you see cygwin's compliance with a Windows
Server security infrastructure?  Is a user limited to just
the same as under windows or can they somehow access other
users data they otherwise couldn't?  I noticed in cygwin 1.7
there is something called LSA Authentication. Does this address
these issues?

Thanks in advance,
DaveLaw


--
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: 1.7.5: Occasional failure of CreatePipe or signal handing due to thread-unsafe code in cwdstuff::set

[Andy Koppe]

On 11 August 2010 20:55, John Carey wrote:
> On Aug 11 01:49 Corinna Vinschen wrote:
>> there's no Win32-safe way to set a new
>> directory handle as cwd in Vista and later anymore.  Since there's no
>> official API to set the cwd using a directory handle, there's no way to
>> set the Win32 cwd to a directory with restricted permissions.
>> This *is* frustrating.
>>
>> I'll look into another solution.  Probably we will have to call
>> SetCurrentDirectory again and ignore any error.  I don't accept the
>> aforementioned restriction for POSIX calls.
>
> So is your idea that if SetCurrentDirectory() fails because
> of path length or permissions, then Cygwin would just accept
> the failure and keep an internal record the
> POSIX current working directory and use that for all
> Cygwin calls, not the Win32 notion of current directory?

Yes. The question then becomes what to do about the Win32 working
directory in that case.

Andy

--
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