Why am I still getting 'unknown primary or operator" on the -L primary of 'find'?
This has persisted since Yosemite, and is still happening on Sierra. According the the man-page, this is supposed to be a legal option. Is it possible I'm using it in the wrong place in the command?
find -L . -name spotstop
I replied to Barney-15E, and let me add that in my sample, the 'spotstop' file is a symlink. Today, the same command on Yosemite went on for over 40 seconds before I terminated it with crtl-C. find -L . -name stopspot
And here's more information ... When done WITHOUT the -L, the command completes in a few seconds.
Here are the files involved:
==> ls -l spotstop stopspot
-rwxrwxrwx 1 dickguertin admin 2970 Oct 31 2015 spotstop
lrwxr-xr-x 1 dickguertin admin 8 Nov 30 2012 stopspot -> spotstop
I don't get any errors. What shell are you using?
FWIW, I'm not getting an error in the Terminal.
I'm using 'bash' on both Yosemite & Sierra. /usr/bin/find is dated 2014-09-09 on Yosemite, and 2017-07-14 on Sierra. /usr/bash is dated 2014-10-26 on Yosemite, and 2017-07-14 on Sierra.
Why am I still getting 'unknown primary or operator" on the -L primary of 'find'?
