Re: ls returns bad file descriptor

2005-06-15 Thread Shaffer, Kenneth

 Btw, this should be fixed in the next snapshot.

It works in 20050614 snapshot, thanks!

--
Ken Shaffer



 - - - - - - -  Appended by Scientific-Atlanta, Inc.  - - - - - - -  
This e-mail and any attachments may contain information which is confidential, 
proprietary, privileged or otherwise protected by law. The information is 
solely intended for the named addressee (or a person responsible for delivering 
it to the addressee). If you are not the intended recipient of this message, 
you are not authorized to read, print, retain, copy or disseminate this message 
or any part of it. If you have received this e-mail in error, please notify the 
sender immediately by return e-mail and delete it from your computer.


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



check_case:strict problem (was Re: ls returns bad file descriptor)

2005-06-15 Thread Shaffer, Kenneth

Along similar lines as the ls failure on shares with
CYGWIN=check_case:strict, if /etc/passwd has a home directory set to a
share, bash won't even start.

--
Ken Shaffer


 - - - - - - -  Appended by Scientific-Atlanta, Inc.  - - - - - - -  
This e-mail and any attachments may contain information which is confidential, 
proprietary, privileged or otherwise protected by law. The information is 
solely intended for the named addressee (or a person responsible for delivering 
it to the addressee). If you are not the intended recipient of this message, 
you are not authorized to read, print, retain, copy or disseminate this message 
or any part of it. If you have received this e-mail in error, please notify the 
sender immediately by return e-mail and delete it from your computer.

**

Program name: C:\cygwin\bin\bash.exe (pid 1472, ppid 1)

App version:  1005.11, api: 0.116

DLL version:  1005.18, api: 0.130

DLL build:20050614 19:54:25SNP

OS version:   Windows NT-5.0

Heap size:402653184

Date/Time:2005-06-15 09:02:34

**

   97 912 [main] bash 1472 set_myself: myself-dwProcessId 1472

  1001012 [main] bash 1472 time: 1118840554 = time (0)

  9902002 [main] bash 1472 environ_init: 0x490238: !::=::\

  1692171 [main] bash 1472 environ_init: 0x490248: !C:=C:\cygwin\bin

  1402311 [main] bash 1472 environ_init: 0x490260: !Y:=Y:\

  1532464 [main] bash 1472 environ_init: 0x490270: 
ALLUSERSPROFILE=C:\Documents and Settings\All Users

  1442608 [main] bash 1472 environ_init: 0x4902A8: APPDATA=C:\Documents and 
Settings\shaffek\Application Data

  1462754 [main] bash 1472 environ_init: 0x4902E8: 
COMMONPROGRAMFILES=C:\Program Files\Common Files

  1392893 [main] bash 1472 environ_init: 0x490320: COMPUTERNAME=SVTREBOOT

  1463039 [main] bash 1472 environ_init: 0x490340: 
COMSPEC=C:\WINNT\system32\cmd.exe

  1463185 [main] bash 1472 check_case_init: File case checking set to STRICT

   853270 [main] bash 1472 parse_options: check_case (called func)

  1383408 [main] bash 1472 parse_options: returning

   703478 [main] bash 1472 environ_init: 0x490368: CYGWIN=check_case:strict

  1403618 [main] bash 1472 environ_init: 0x4903A0: HOMEDRIVE=Y:

  1593777 [main] bash 1472 environ_init: 0x4903B8: HOMEPATH=\

  2213998 [main] bash 1472 environ_init: 0x4903C8: 
HOMESHARE=\\dsnserv1\shaffek$

  2764274 [main] bash 1472 environ_init: 0x4903F0: LOGONSERVER=\\BCGSERV7

  3164590 [main] bash 1472 environ_init: 0x490410: NUMBER_OF_PROCESSORS=2

  2204810 [main] bash 1472 environ_init: 0x490430: OS=Windows_NT

  1464956 [main] bash 1472 environ_init: 0x490448: 
OS2LIBPATH=C:\WINNT\system32\os2\dll;

  1535109 [main] bash 1472 getwinenv: can't set native for PATH= since no 
environ yet

  1225231 [main] bash 1472 normalize_posix_path: src .

  1005331 [main] bash 1472 mount_info::conv_to_posix_path: 
conv_to_posix_path (C:\cygwin\bin, no-keep-rel, no-add-slash)

   745405 [main] bash 1472 normalize_win32_path: C:\cygwin\bin = 
normalize_win32_path (C:\cygwin\bin)

   805485 [main] bash 1472 mount_info::conv_to_posix_path: /usr/bin = 
conv_to_posix_path (C:\cygwin\bin)

   995584 [main] bash 1472 cwdstuff::get: posix /usr/bin

   725656 [main] bash 1472 cwdstuff::get: (/usr/bin) = cwdstuff::get 
(0x22EBC0, 260, 1, 0), errno 0

   735729 [main] bash 1472 normalize_posix_path: /usr/bin/ = 
normalize_posix_path (.)

   715800 [main] bash 1472 mount_info::conv_to_win32_path: 
conv_to_win32_path (/usr/bin)

   895889 [main] bash 1472 set_flags: flags: binary (0x2)

   745963 [main] bash 1472 mount_info::conv_to_win32_path: src_path 
/usr/bin, dst C:\cygwin\bin, flags 0xA, rc 0

  3156278 [main] bash 1472 symlink_info::check: not a symlink

   946372 [main] bash 1472 symlink_info::check: 0 = symlink.check 
(C:\cygwin\bin, 0x22E880) (0xA)

   846456 [main] bash 1472 mount_info::conv_to_win32_path: 
conv_to_win32_path (/usr)

   766532 [main] bash 1472 set_flags: flags: binary (0x2)

   776609 [main] bash 1472 mount_info::conv_to_win32_path: src_path /usr, 
dst C:\cygwin\usr, flags 0xA, rc 0

  2386847 [main] bash 1472 symlink_info::check: not a symlink

   796926 [main] bash 1472 symlink_info::check: 0 = symlink.check 
(C:\cygwin\usr, 0x22E880) (0xA)

  6477573 [main] bash 1472 set_privilege: 1 = set_privilege ((token 310) 
SeChangeNotifyPrivilege, 1)

  2657838 [main] bash 1472 path_conv::check: this-path(C:\cygwin\bin), 
has_acls(1)

  1678005 [main] bash 1472 mount_info::conv_to_posix_path: 
conv_to_posix_path (C:\WINNT\system32, keep-rel, no-add-slash)

   738078 [main] bash 1472 normalize_win32_path: C:\WINNT\system32 = 
normalize_win32_path (C:\WINNT\system32)

   788156 [main] bash 1472 mount_info::conv_to_posix_path: 
/cygdrive/c/WINNT/system32 = 

Re: ls returns bad file descriptor

2005-06-15 Thread Pierre A. Humblet

- Original Message - 
From: Igor Pechtchanski 
To: Pierre A. Humblet 
Cc: cygwin@cygwin.com
Sent: Tuesday, June 14, 2005 7:49 PM
Subject: Re: ls returns bad file descriptor


 On Tue, 14 Jun 2005, Pierre A. Humblet wrote:
 
   Please don't.  Try doing this instead:
  
c:\strace -ostrace.out bash
shaffekcd //explr_drivers5/reboot_results2
reboot_results2
shaffekls
 
   Attached.
 
  Try turning off strict case checking.
 
 Pierre, would you mind elaborating on exactly what in that strace pointed
 you to strict case checking being the culprit?  I've looked through it,
 but perhaps I missed something...  Thanks.

Exactly what Chris explained in.
http://cygwin.com/ml/cygwin/2005-06/msg00653.html

Pierre


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



Re: check_case:strict problem (was Re: ls returns bad file descriptor)

2005-06-15 Thread Christopher Faylor
On Wed, Jun 15, 2005 at 09:08:40AM -0400, Shaffer, Kenneth wrote:
Along similar lines as the ls failure on shares with
CYGWIN=check_case:strict, if /etc/passwd has a home directory set to a
share, bash won't even start.

WJFFM.  There was a problem pre-snapshot but bash still started.  Now I
get no errors.

cgf

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



Re: ls returns bad file descriptor

2005-06-14 Thread Shankar Unni

Shaffer, Kenneth wrote:

After changing to a directory on another computer, I get bad file
descriptor from an ls command:

shaffekcd //explr_drivers5/reboot_results2
reboot_results2
shaffekls
ls: reading directory .: Bad file descriptor


I don't see this on my WinXP SP2 box running 1.5.17.

Perhaps there's some problem/issue with the permissions on the root of 
your share that's confusing bash?  Does this also happen in a 
subdirectory of the share?



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



Re: ls returns bad file descriptor

2005-06-14 Thread Shaffer, Kenneth

 Perhaps there's some problem/issue with the permissions on the root of
 your share that's confusing bash? Does this also happen in a
 subdirectory of the share?

bash hasn't changed, only cygwin1.dll.

It also happens in a subdirectory of the share.  I had posted an strace
output which I hope would make sense to others more knowledgeable than
myself.

When I looked at the strace output, it appears to me it read the home
directory instead of the share directory, but never output that. It's as
if the cwd got changed from what the PWD environment variable says it is.

This doesn't happen with 1.5.16 using the same bash.

I'm going to try a different snapshot.

--
Ken Shaffer



 - - - - - - -  Appended by Scientific-Atlanta, Inc.  - - - - - - -  
This e-mail and any attachments may contain information which is confidential, 
proprietary, privileged or otherwise protected by law. The information is 
solely intended for the named addressee (or a person responsible for delivering 
it to the addressee). If you are not the intended recipient of this message, 
you are not authorized to read, print, retain, copy or disseminate this message 
or any part of it. If you have received this e-mail in error, please notify the 
sender immediately by return e-mail and delete it from your computer.


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



Re: ls returns bad file descriptor

2005-06-14 Thread Christopher Faylor
On Tue, Jun 14, 2005 at 04:14:41PM -0400, Shaffer, Kenneth wrote:
On Tue, Jun 14, 2005 at 10:17:09AM -0700, Shankar Unni wrote:
Perhaps there's some problem/issue with the permissions on the root of
your share that's confusing bash?  Does this also happen in a
subdirectory of the share?

bash hasn't changed, only cygwin1.dll.

It also happens in a subdirectory of the share.  I had posted an strace
output which I hope would make sense to others more knowledgeable than
myself.

When I looked at the strace output, it appears to me it read the home
directory instead of the share directory, but never output that.  It's
as if the cwd got changed from what the PWD environment variable says
it is.

You didn't notice (or report) that you got no error message when running
under strace?  Hmm.

The reason is that strace isn't a cygwin program and it does not necessarily
inherit cygwin's concept of cwd.

This doesn't happen with 1.5.16 using the same bash.

I'm going to try a different snapshot.

Please don't.  Try doing this instead:

  c:\strace -ostrace.out bash
  shaffekcd //explr_drivers5/reboot_results2
  reboot_results2
  shaffekls

and send strace.out here.

cgf

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



Re: ls returns bad file descriptor

2005-06-14 Thread Pierre A. Humblet
 Please don't.  Try doing this instead:

  c:\strace -ostrace.out bash
  shaffekcd //explr_drivers5/reboot_results2
  reboot_results2
  shaffekls

 Attached.

Try turning off strict case checking.

Pierre




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



Re: ls returns bad file descriptor

2005-06-14 Thread Shaffer, Kenneth

 Try turning off strict case checking.

That works, but now I'm not unix-like.

I put the strict case back and then tried the case that Windows shows in
the explorer, Explr_drivers5\Reboot_results2, and ls still failed.

In any event, looks like we're closer to solving the problem.

--
Ken Shaffer



 - - - - - - -  Appended by Scientific-Atlanta, Inc.  - - - - - - -  
This e-mail and any attachments may contain information which is confidential, 
proprietary, privileged or otherwise protected by law. The information is 
solely intended for the named addressee (or a person responsible for delivering 
it to the addressee). If you are not the intended recipient of this message, 
you are not authorized to read, print, retain, copy or disseminate this message 
or any part of it. If you have received this e-mail in error, please notify the 
sender immediately by return e-mail and delete it from your computer.


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



Re: ls returns bad file descriptor

2005-06-14 Thread Christopher Faylor
On Tue, Jun 14, 2005 at 05:24:59PM -0400, Pierre A. Humblet wrote:
 Please don't.  Try doing this instead:

  c:\strace -ostrace.out bash
  shaffekcd //explr_drivers5/reboot_results2
  reboot_results2
  shaffekls

 Attached.

Try turning off strict case checking.

Wow.  I'm glad you noticed this.  I completely missed it.  Thank you.

cgf

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



Re: ls returns bad file descriptor

2005-06-14 Thread Igor Pechtchanski
On Tue, 14 Jun 2005, Pierre A. Humblet wrote:

  Please don't.  Try doing this instead:
 
   c:\strace -ostrace.out bash
   shaffekcd //explr_drivers5/reboot_results2
   reboot_results2
   shaffekls

  Attached.

 Try turning off strict case checking.

Pierre, would you mind elaborating on exactly what in that strace pointed
you to strict case checking being the culprit?  I've looked through it,
but perhaps I missed something...  Thanks.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

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



Re: ls returns bad file descriptor

2005-06-14 Thread Christopher Faylor
On Tue, Jun 14, 2005 at 07:49:42PM -0400, Igor Pechtchanski wrote:
On Tue, 14 Jun 2005, Pierre A. Humblet wrote:

  Please don't.  Try doing this instead:
 
   c:\strace -ostrace.out bash
   shaffekcd //explr_drivers5/reboot_results2
   reboot_results2
   shaffekls

  Attached.

 Try turning off strict case checking.

Pierre, would you mind elaborating on exactly what in that strace pointed
you to strict case checking being the culprit?  I've looked through it,
but perhaps I missed something...  Thanks.

I don't know if Pierre picked up on something else (or maybe just looked
at the cygcheck output) but a clue was the fact that path_conv::check
kept inspecting components of the path even after a valid path was
detected.  I was working my way there when I wisely decided to check the
mailing list and saw Pierre's insight.  It's supposed to stop looking at
the path once it finds a valid path, except in the case of non-relaxed
case checking, i.e., this is one of a few slowdowns in the case checking
code.

cgf

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



Re: ls returns bad file descriptor

2005-06-14 Thread Christopher Faylor
On Tue, Jun 14, 2005 at 07:52:45PM -0400, Christopher Faylor wrote:
On Tue, Jun 14, 2005 at 07:49:42PM -0400, Igor Pechtchanski wrote:
On Tue, 14 Jun 2005, Pierre A. Humblet wrote:

  Please don't.  Try doing this instead:
 
   c:\strace -ostrace.out bash
   shaffekcd //explr_drivers5/reboot_results2
   reboot_results2
   shaffekls

  Attached.

 Try turning off strict case checking.

Pierre, would you mind elaborating on exactly what in that strace pointed
you to strict case checking being the culprit?  I've looked through it,
but perhaps I missed something...  Thanks.

I don't know if Pierre picked up on something else (or maybe just looked
at the cygcheck output) but a clue was the fact that path_conv::check
kept inspecting components of the path even after a valid path was
detected.  I was working my way there when I wisely decided to check the
mailing list and saw Pierre's insight.  It's supposed to stop looking at
the path once it finds a valid path, except in the case of non-relaxed
case checking, i.e., this is one of a few slowdowns in the case checking
code.

Btw, this should be fixed in the next snapshot.

cgf

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