topic Re: Any syntax errors in this command? in Operating System - HP-UX

Any syntax errors in this command?

MAD_2 — Fri, 17 May 2002 16:05:36 GMT

I am writing a script that looks for specific owner files that are so many days old and it skips files I don't want to include in the list for each user. The syntax goes like this:

find . -type f -user $USER -mtime +90 | grep -v '^.sh$' | grep -v '^.pl$' | gre
p -v '^.sql$' >> $LOGFILE.$USER.log

However, I am not obtaining the expected result, which should exclude all files with the following pattern *.sh* *.pl* and *.sql*. Why? Where did I go wrong? Any hints?

Thanks...

Re: Any syntax errors in this command?

Sridhar Bhaskarla — Fri, 17 May 2002 16:15:10 GMT

Mynor,

Use "set -x" before executing the command and verify how it is resolving your pattern matching.

I would think of taking out single quotes and replacing ^ and $ with the wild char *.

-Sri

Re: Any syntax errors in this command?

S.K. Chan — Fri, 17 May 2002 16:24:59 GMT

Like Sri said that would work for you. You can also be specific about the "." by using ..

grep -v *\.sh*

.. for example

Re: Any syntax errors in this command?

Rodney Hills — Fri, 17 May 2002 16:25:57 GMT

I would remove the "^" in the grep's. They are anchoring to the beginning of line, which I don't think you want.

find . -type f -user $USER -mtime +90 | grep -v '.sh$' | grep -v '.pl$' | grep -v '.sql$' >> $LOGFILE.$USER.log

-- Rod Hills

Re: Any syntax errors in this command?

MAD_2 — Fri, 17 May 2002 16:30:20 GMT

The pattern specified by Rodney works for instances such as *.sh or *.sql but not for those like *.sh.* or *.sh_* That's what I was using at first and it skips the *.sh files, which is part of what I want. However, there are also files with patterns such as *.sh.YYYYMMDD or *.sh_YYYYMMDD and I want those excluded from the search too.

Re: Any syntax errors in this command?

Sanjay_6 — Fri, 17 May 2002 16:35:52 GMT

Hi Mynor,

Try this,

find . -type f -user $USER -mtime +90 | grep -v '\.sh$' | grep -v '\.pl$' | grep -v '\.sql$' >> $LOGFILE.$USER.log

Hope this helps.

regds

Re: Any syntax errors in this command?

John Palmer — Fri, 17 May 2002 16:36:48 GMT

Try this as the grep (only one is required):

grep -v -e \.sh -e \.pl -e \.sql

Regards,
John

Re: Any syntax errors in this command?

Rodney Hills — Fri, 17 May 2002 16:40:12 GMT

If you use extended regular expressions (available with -E option on grep), you can be more detailed on what to choose-

find ... | grep -v -E "\.[sql|pl|sh]([._][0-9]*)*" >logfile

-- Rod Hills

Re: Any syntax errors in this command?

Rodney Hills — Fri, 17 May 2002 16:42:40 GMT

Oops, forgot dollar sign on end

find ... | grep -v -E "\.[sql|pl|sh]([._][0-9]*)*$" >logfile

-- Rod Hills

Re: Any syntax errors in this command?

MAD_2 — Fri, 17 May 2002 16:48:47 GMT

Perfect Rodney, my question is answered... Just what I was looking for.

Re: Any syntax errors in this command?

James R. Ferguson — Fri, 17 May 2002 16:54:24 GMT

Hi:

Your original expression meant to match the patterns as achored at both the beginning and the ending of a line -- i.e. strings that constitute the whole line. Returning filenames from the current directory would yield strings beginning with "./" too.

Regards!

...JRF...