On Mon 4/3/06 13:19 EDT cyg wrote: > On Mon, Apr 03, 2006 at 10:52:01AM -0500, Tom Rodman wrote: > >Then, I ran: > > > > C:\>c:\aut\cyg\bin\strace -o/tmp/strace.out /bin/bash > > bash-3.00$ exec /bin/ls -l /etc/passwd > > The strace shows that /bin/ls is a shell script. I suspect that's at least > part of your problem. Maybe you have both a /bin/ls and a /bin/ls.exe?
your right: /bin $ uname -a; ls -ld ls ls.exe CYGWIN_NT-5.0 c7mkes108 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin -rw-rw-r-- 1 scmcron SCM_ES_STAFF 0 Dec 26 11:33 ls -r-xr-xr-x+ 1 build Users 91136 Feb 14 08:22 ls.exe* Not sure how a zero byte /bin/ls file was created. - my WAG: it was the result of a "cut and paste" accident back on Dec 26 at the bash commandline; or some other badly formed interactive bash commandline. My bash PS1 env var ends with "> " - I'm going to fix that! If I had pasted multiple lines from my window scroll history, the leading "> " would have resulted in a zero byte file for each "arg 0" in the scroll history - that had been mistakely pasted into a bash session. The new snapshot is working fine now that the 0 byte /bin/ls file is gone: ~ $ date;uname -a; ls -l /etc/passwd Mon Apr 3 12:57:42 CDT 2006 CYGWIN_NT-5.0 c7mkes108 1.5.20s(0.155/4/2) 20060329 23:02:10 i686 Cygwin -rw-rw-r-- 1 scmcron SCM_ES_STAFF 47822 Apr 3 06:51 /etc/passwd I've saved the strace test and output snippet for future reference. I'll locate and fix all other bogus 0 byte files (if any), with: find /usr -type f -empty |egrep -v '\.bs$' Thanks for your patience, and follow through! -- Tom > > 513 13523662 [main] bash 5608 spawn_guts: priority class 32 > > 240 13523902 [main] bash 5608 fhandler_console::need_invisible: > > invisible_console 0 > > 144 13524046 [main] bash 5608 spawn_guts: null_app_name 0 > > (c:\aut\cyg\bin\sh.exe, c:\aut\cyg\bin\sh.exe /bin/ls -l /etc/passwd) > > 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/