Okay, this has bothered me for ages and I'm finally asking if anyone can
explain why does find sometimes crap itself over certain paths. eg
find /opt/spool/smtpd/spam -name smtpd00*
find: paths must preceed expressions
I usally do some work acound. I think it requires me to move to another
On Thu, Dec 11, 2003 at 12:43:25 +1100, Terry Collins wrote:
find /opt/spool/smtpd/spam -name smtpd00*
find: paths must preceed expressions
There are at least two files matching 'smtpd00*' in your current
directory and your shell is expanding the wildcard. *Always* escape
or quote wildcards
On Thu, Dec 11, 2003 at 01:17:36 +1100, Benno wrote:
On Thu Dec 11, 2003 at 12:55:46 +1100, John Clarke wrote:
The shell will only pass them unchanged if it can't find a match.
And some shells (like my zsh setup) don't even do that.
What does it do instead?
Cheers,
John
--
whois
On Thu Dec 11, 2003 at 13:27:33 +1100, John Clarke wrote:
On Thu, Dec 11, 2003 at 01:17:36 +1100, Benno wrote:
On Thu Dec 11, 2003 at 12:55:46 +1100, John Clarke wrote:
The shell will only pass them unchanged if it can't find a match.
And some shells (like my zsh setup) don't even do that.
quote who=John Clarke
On Thu, Dec 11, 2003 at 01:17:36 +1100, Benno wrote:
On Thu Dec 11, 2003 at 12:55:46 +1100, John Clarke wrote:
The shell will only pass them unchanged if it can't find a match.
And some shells (like my zsh setup) don't even do that.
What does it do instead?
