grep = * vs grep = * > foo
Hello, >From the XP Pro command prompt, grepping for = (thru ini files) produces the expected lists. In the directory with the following files [C:\Development\test] .dir 8/23/2002 17:07 0 control.ini 9/13/2002 10:52 213 cr8demo.INI 8/13/1996 8:18 848 CTELSVR.INI 8/26/2002 11:15 165 Ctelwin.ini 8/23/2001 5:00 2 desktop.ini 4/24/1998 0:00 218 FRONTPG.INI 9/12/2002 16:31 169 hpbafd.ini 10/02/2002 9:57 871 INTELDAT.INI 6/05/1998 15:12 0 Isdbg.ini 9/11/2002 17:31 126 mdm.ini 10/02/2002 9:28 0 Migm30.INI 8/23/2001 5:00 1,405 msdfmap.ini 9/13/2002 10:54 32 People.INI 9/03/2002 10:00 0 PROTOCOL.INI 9/13/2002 10:34 52 PwInstall.in 8/26/2002 12:06 61 smscfg.ini 10/01/2002 11:08 993 SWDEPEND.INI 9/12/2002 9:20 231 system.ini 10/01/2002 10:12 32 Trace.INI 9/23/2002 11:39 1,015 win.ini 9/24/2002 10:15 50 Winamp.ini 9/24/2002 11:57 41 winampa.ini .grep = * CTELSVR.INI:PageTimeout=50 CTELSVR.INI:MaxBufferSize=256 CTELSVR.INI:LockRetry=10 CTELSVR.INI:CommitLockRetry=10 CTELSVR.INI:ReadAheadPages=0 CTELSVR.INI:Deleted=On CTELSVR.INI:QueryTimeout=120 CTELSVR.INI:LoginTimeout=20 CTELSVR.INI:ConnectionTimeout=0 CTELSVR.INI:UpdateRetries=7 CTELSVR.INI:OptimisticLocking=1 Ctelwin.ini:NetPath=\\IMS-MSSQL\CTLWIN\ Ctelwin.ini:LocalPath=C:\Program Files\Epicor\Clientele Local Files\ Ctelwin.ini:ProgramFolder=Epicor\Clientele 7.2 Ctelwin.ini:UserName= Ctelwin.ini:Password= cr8demo.INI:Maximize=No cr8demo.INI:XPos=100 cr8demo.INI:YPos=49 cr8demo.INI:Maximize=No cr8demo.INI:XPos=85 cr8demo.INI:YPos=56 cr8demo.INI:Maximize=No cr8demo.INI:XPos=44 cr8demo.INI:YPos=54 cr8demo.INI:Height=194 cr8demo.INI:Width=397 cr8demo.INI:ReportPathName= cr8demo.INI:Sectors=0 ... and so on But... grepping and redircting the output to a file causes a process loop that has to be killed 17:17 0 [C:\Development\test] .grep = * > delme 17:18 66048 [C:\Development\test] .^C What happens is that the grep starts reading the delme file and then reporting all those finds... Ok, but the odd part this is, this behavior doesn't appear when using the bash shell (on the same XP box). Thoughts or explanations? -Sheryl __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: grep = * vs grep = * > foo
On Tue, Oct 08, 2002 at 05:23:05PM -0700, Sheryl McKeown wrote: >grepping and redircting the output to a file >causes a process loop that has to be killed > >17:17 0 [C:\Development\test] >.grep = * > delme > >17:18 66048 [C:\Development\test] >.^C > >What happens is that the grep starts reading the delme >file and then reporting all those finds... Right. The file is created before grep is started so when grep expands the '*' if finds delme and dutifully searches it... forever. >Ok, but the odd part this is, this behavior doesn't appear when using >the bash shell (on the same XP box). When run from the bash shell, bash itself first expands '*' and then creates delme. Since delme doesn't exist, it isn't searched. cgf -- Please do not send me personal email with cygwin questions. Use the resources at http://cygwin.com/ . -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: grep = * vs grep = * > foo
Thanks, cgf, That makes sense. But one more comment "grep = *.* > delme" from the XP prompt does NOT create the infinite loop. It acts like the bash shell. -Sheryl --- Christopher Faylor <[EMAIL PROTECTED]> wrote: > On Tue, Oct 08, 2002 at 05:23:05PM -0700, Sheryl > McKeown wrote: > >grepping and redircting the output to a file > >causes a process loop that has to be killed > > > >17:17 0 [C:\Development\test] > >.grep = * > delme > > > >17:18 66048 [C:\Development\test] > >.^C > > > >What happens is that the grep starts reading the > delme > >file and then reporting all those finds... > > Right. The file is created before grep is started > so when grep expands > the '*' if finds delme and dutifully searches it... > forever. > > >Ok, but the odd part this is, this behavior doesn't > appear when using > >the bash shell (on the same XP box). > > When run from the bash shell, bash itself first > expands '*' and then > creates delme. Since delme doesn't exist, it isn't > searched. > > cgf > -- > Please do not send me personal email with cygwin > questions. > Use the resources at http://cygwin.com/ . > > -- > Unsubscribe info: > http://cygwin.com/ml/#unsubscribe-simple > Bug reporting: http://cygwin.com/bugs.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: grep = * vs grep = * > foo
>Thanks, cgf, That makes sense. > >But one more comment > >"grep = *.* > delme" from the XP prompt does NOT >create the infinite loop. It acts like the bash >shell. well obviously - delme doesnt contain a period. Gareth _ Send and receive Hotmail on your mobile device: http://mobile.msn.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: grep = * vs grep = * > foo
Hi Gareth, That makes sense in the Unix world, but in this particular XP directory *.* returns the same listing as * As you note though, grep = * > delme and grep = *.* > delme.txt both create an infinite loop. But, "grep = *.* > delme." does not create the loop. -Sheryl --- Gareth Pearce <[EMAIL PROTECTED]> wrote: > > >Thanks, cgf, That makes sense. > > > >But one more comment > > > >"grep = *.* > delme" from the XP prompt does NOT > >create the infinite loop. It acts like the bash > >shell. > > well obviously - delme doesnt contain a period. > > Gareth > > _ > Send and receive Hotmail on your mobile device: > http://mobile.msn.com > > > -- > Unsubscribe info: > http://cygwin.com/ml/#unsubscribe-simple > Bug reporting: http://cygwin.com/bugs.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: grep = * vs grep = * > foo
On Tue, Oct 08, 2002 at 05:41:18PM -0700, Sheryl McKeown wrote: >That makes sense in the Unix world, but in this particular XP directory >*.* returns the same listing as * > >As you note though, >grep = * > delme and >grep = *.* > delme.txt >both create an infinite loop. > >But, "grep = *.* > delme." does not create the loop. Gareth is correct. If you do this: touch delme ls *.* You'll see that delme is not listed. Cygnus wildcard expansion follows UNIX rules, not MS-DOS rules. You can't (easily) create an actual 'delme.' file on Windows. So, "delme." is the same thing as "delme", i.e. if you perform an ls on the directory, you'll see a file called "delme" not "delme.". cgf >--- Gareth Pearce <[EMAIL PROTECTED]> wrote: >> >> >Thanks, cgf, That makes sense. >> > >> >But one more comment >> > >> >"grep = *.* > delme" from the XP prompt does NOT >> >create the infinite loop. It acts like the bash >> >shell. >> >> well obviously - delme doesnt contain a period. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: grep = * vs grep = * > foo
Gotch ya. Thanks Christopher and Gareth. And the . makes all the difference. Best, Sheryl --- Christopher Faylor <[EMAIL PROTECTED]> wrote: > On Tue, Oct 08, 2002 at 05:41:18PM -0700, Sheryl > McKeown wrote: > >That makes sense in the Unix world, but in this > particular XP directory > >*.* returns the same listing as * > > > >As you note though, > >grep = * > delme and > >grep = *.* > delme.txt > >both create an infinite loop. > > > >But, "grep = *.* > delme." does not create the > loop. > > Gareth is correct. > > If you do this: > > touch delme > ls *.* > > You'll see that delme is not listed. Cygnus > wildcard expansion follows > UNIX rules, not MS-DOS rules. You can't (easily) > create an actual > 'delme.' file on Windows. So, "delme." is the same > thing as "delme", i.e. > if you perform an ls on the directory, you'll see a > file called "delme" > not "delme.". > > cgf > > >--- Gareth Pearce <[EMAIL PROTECTED]> wrote: > >> > >> >Thanks, cgf, That makes sense. > >> > > >> >But one more comment > >> > > >> >"grep = *.* > delme" from the XP prompt does NOT > >> >create the infinite loop. It acts like the bash > >> >shell. > >> > >> well obviously - delme doesnt contain a period. > > -- > Unsubscribe info: > http://cygwin.com/ml/#unsubscribe-simple > Bug reporting: http://cygwin.com/bugs.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: grep = * vs grep = * > foo
On Tue, Oct 08, 2002 at 08:27:31PM -0400, Christopher Faylor wrote: > On Tue, Oct 08, 2002 at 05:23:05PM -0700, Sheryl McKeown wrote: > >grepping and redircting the output to a file > >causes a process loop that has to be killed > > > >17:17 0 [C:\Development\test] > >.grep = * > delme > > > >17:18 66048 [C:\Development\test] > >.^C > > > >What happens is that the grep starts reading the delme > >file and then reporting all those finds... > > Right. The file is created before grep is started so when grep expands > the '*' if finds delme and dutifully searches it... forever. > > >Ok, but the odd part this is, this behavior doesn't appear when using > >the bash shell (on the same XP box). > > When run from the bash shell, bash itself first expands '*' and then > creates delme. Since delme doesn't exist, it isn't searched. Would a similar endless loop occur if delme did exist and the redirection overwrote it? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: grep = * vs grep = * > foo
On Wed, Oct 09, 2002 at 01:42:02AM -0400, Jon LaBadie wrote: >On Tue, Oct 08, 2002 at 08:27:31PM -0400, Christopher Faylor wrote: >> On Tue, Oct 08, 2002 at 05:23:05PM -0700, Sheryl McKeown wrote: >> >grepping and redircting the output to a file >> >causes a process loop that has to be killed >> > >> >17:17 0 [C:\Development\test] >> >.grep = * > delme >> > >> >17:18 66048 [C:\Development\test] >> >.^C >> > >> >What happens is that the grep starts reading the delme >> >file and then reporting all those finds... >> >> Right. The file is created before grep is started so when grep expands >> the '*' if finds delme and dutifully searches it... forever. >> >> >Ok, but the odd part this is, this behavior doesn't appear when using >> >the bash shell (on the same XP box). >> >> When run from the bash shell, bash itself first expands '*' and then >> creates delme. Since delme doesn't exist, it isn't searched. > >Would a similar endless loop occur if delme did exist >and the redirection overwrote it? Yes. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: grep = * vs grep = * > foo
On 9-10-2002 2:58, Christopher Faylor wrote: > > You'll see that delme is not listed. Cygnus wildcard expansion follows (snip) Cygnus? Who's that? ;-) - Michael -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: grep = * vs grep = * > foo
On Wed, Oct 09, 2002 at 01:15:01PM +0200, Michael Schaap wrote: >On 9-10-2002 2:58, Christopher Faylor wrote: >> >>You'll see that delme is not listed. Cygnus wildcard expansion follows >(snip) > >Cygnus? Who's that? ;-) OOPS! Slap! How embarrassing. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
