System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

find commad throws error "find: missing conjunction"

Kaps_2
Regular Advisor

find commad throws error "find: missing conjunction"

hi the below find command throws error "find: missing conjunction"

find / -mtime +180 ! -type d ! -type l -size +10485760c -printf "%s¥t%t¥t%a¥t%u¥t%p¥n" > file.txt

5 REPLIES
Steven Schweda
Honored Contributor

Re: find commad throws error "find: missing conjunction"

> find commad throws error [...]

On what?

sizer -v

Whose "find" are you using? "-printf"?

What's that in ASCII?

If you want GNU "find", then you may need to
install GNU findutils.

http://www.gnu.org/software/findutils/
Pieter 't Hart
Honored Contributor

Re: find commad throws error "find: missing conjunction"

find has a -print option, not -printf?

maybe you ment |printf instead of -printf ?
Steven Schweda
Honored Contributor

Re: find commad throws error "find: missing conjunction"

> maybe you ment |printf instead of -printf ?

More likely a GNU "find" user, I claim.

http://www.gnu.org/software/findutils/manual/html_node/find_html/Print-File-Information.html

GNU utilities seem to be getting developed at
a faster rate than Tru64 utilities.
Kapil Jha
Honored Contributor

Re: find commad throws error "find: missing conjunction"

I suppose its not becaouse of printf or print

Can you try to run
#find / -mtime +180 ! -type d ! -type l -size +10485760c

and see if its giving output
Run it from / directory.

BR,
Kapil+
I am in this small bowl, I wane see the real world......
Steven Schweda
Honored Contributor

Re: find commad throws error "find: missing conjunction"

> I suppose its not becaouse of printf or print

You seem to be working very hard to avoid the
simplest explanation.

Of course, the original problem report is so
poor that it's hard to know much. Around
here, for example:

urtx# find / -mtime +180 ! -type d ! -type l -size +10485760c -printf "any_string"
find: bad option -printf

So it's not at all clear that we even know
which OS (or "find" program) is involved
here. I'm not equipped to investigate a
command, which I can't even _read_ with any
confidence, on every old HP-UX version which
might be in use somewhere.

And, judging by the frequency of his
responses, the original poster doesn't really
care.