Re: IFS gotcha - potential disaster

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Thanks, Barbara - I guess this suppresses the expansion of wildcards, eh? I 
forgot about that in a Unix-style setting.

Vern

At 09:49 AM 12/15/2003 -0500, you wrote:
> Vern Hamberg wrote:
> >
> > I don't know if this has happened to anyone else, but it was a little
> > messy. Somehow we got a file in the root (/) of our system, named *.* -
> > perhaps as the destination of some kind of copy command.
> >
> > Anyway, when clicking, in Ops Nav, on the "root" share we have, only that
> > "file" showed up. Of course, if I did a WRKLNK '/*.*', all the files with a
> > period somewhere in the name appeared, including this one.
> >
> > In QShell, ls ??? (for 3-character names) displayed this file, as well as
> > the directories with 3-letter names, such as "tmp" and "usr", and their
> > subtrees - fortunately there is not much in these right now.
> >
>
> In QSH, use the back-slash to escape the special characters.
>
> > ls 
> \*\.\*
>
> *.*
>
> $
> > cat 
> \*\.\*
>
> abc
>
> $
> > 
> rm  \*\.\*
>
> $
> > ls 
> \*\.\*
>   ls: 001-2113 Error found getting information for object *.*. No such
> path or
>
> directory.
>
> $