ANNOUNCE: WLUG meeting is one week away
The Waikato Linux Users Group have a meeting in one week from today: ---------------------------------------------------------------------- To be announced... October 18th 7:30pm MS4.G.02 (http://www.waikato.ac.nz/contacts/map?MS4)
Can someone update the meeting page plzkthx? On 11 October 2010 06:26, Meeting Reminder Bot <bot(a)wlug.org.nz> wrote:
The Waikato Linux Users Group have a meeting in one week from today:
---------------------------------------------------------------------- To be announced...
October 18th 7:30pm MS4.G.02 (http://www.waikato.ac.nz/contacts/map?MS4) _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
-- Disclaimer: By sending an email to any of my addresses you are agreeing that: 1. I am by definition, "the intended recipient" 2. All information in the email is mine to do with as I see fit and make such financial profit, political mileage, or good joke as it lends itself to. 3. I may take the contents as representing the views of your company. 4. This overrides any disclaimer or statement of confidentiality that may be included on your message.
Sure. On Sun, Oct 10, 2010 at 8:46 PM, Bruce Kingsbury <zcat(a)zcat.geek.nz> wrote:
Can someone update the meeting page plzkthx?
On 11 October 2010 06:26, Meeting Reminder Bot <bot(a)wlug.org.nz> wrote:
The Waikato Linux Users Group have a meeting in one week from today:
---------------------------------------------------------------------- To be announced...
October 18th 7:30pm MS4.G.02 (http://www.waikato.ac.nz/contacts/map?MS4) _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
-- Disclaimer: By sending an email to any of my addresses you are agreeing that: 1. I am by definition, "the intended recipient" 2. All information in the email is mine to do with as I see fit and make such financial profit, political mileage, or good joke as it lends itself to. 3. I may take the contents as representing the views of your company. 4. This overrides any disclaimer or statement of confidentiality that may be included on your message. _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
Hi I was wondering if someone could help with the output of find in a simple bash script. I need to output the file create date and time from the following script. The purpose of this script is to find an order number and check if that has been received by the system. If it does then it needs to return the date and time the file was archived if it doesn't then it shows a message saying that it cant find it in the archive. find /home/archive/* -mtime -90 |\ xargs grep -l $searchstring previously I was piping the output of the grep command to ls -lath and that was sufficient but there are too may files in the directory now that it dies. Cheers Cameron
Why not find -iname \*$searchstring\* /home/archive/ ? On Mon, Oct 11, 2010 at 8:58 PM, Cameron Rangeley < Cameron.Rangeley(a)turnstone.co.nz> wrote:
Hi
I was wondering if someone could help with the output of find in a simple bash script.
I need to output the file create date and time from the following script. The purpose of this script is to find an order number and check if that has been received by the system. If it does then it needs to return the date and time the file was archived if it doesn't then it shows a message saying that it cant find it in the archive.
find /home/archive/* -mtime -90 |\ xargs grep -l $searchstring
previously I was piping the output of the grep command to ls -lath and that was sufficient but there are too may files in the directory now that it dies.
Cheers
Cameron _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
On 15 October 2010 07:16, Craig Box <craig(a)dubculture.co.nz> wrote:
Why not find -iname \*$searchstring\* /home/archive/
My reading of it, they're looking for the string within all the files not just in the filename. But if they have that many records I'd seriously start looking at putting all the information into an sql database or something.
I was wondering if someone could help with the output of find in a simple bash script.
I need to output the file create date and time from the following script. The purpose of this script is to find an order number and check if that has been received by the system. If it does then it needs to return the date and time the file was archived if it doesn't then it shows a message saying that it cant find it in the archive.
find /home/archive/* -mtime -90 |\ xargs grep -l $searchstring
previously I was piping the output of the grep command to ls -lath and that was sufficient but there are too may files in the directory now that it dies.
Not sure whether this works on such large amounts of files... Instead of piping the filenames into "xargs/grep", just use the "-exec" option of the "find" command to execute "grep". Also, read line by line of the file matches from stdin when using "ls -lath". find /home/archive/* -mtime -90 \ -exec grep -l "$searchstring" {} \; | \ while read file; do ls -lath $file; done; Cheers, Peter -- Peter Reutemann, Dept. of Computer Science, University of Waikato, NZ http://www.cs.waikato.ac.nz/~fracpete/ Ph. +64 (7) 858-5174
On 15 October 2010 09:00, Peter Reutemann <fracpete(a)waikato.ac.nz> wrote:
I was wondering if someone could help with the output of find in a simple bash script.
I need to output the file create date and time from the following script. The purpose of this script is to find an order number and check if that has been received by the system. If it does then it needs to return the date and time the file was archived if it doesn't then it shows a message saying that it cant find it in the archive.
find /home/archive/* -mtime -90 |\ xargs grep -l $searchstring
previously I was piping the output of the grep command to ls -lath and that was sufficient but there are too may files in the directory now that it dies.
Not sure whether this works on such large amounts of files... Instead of piping the filenames into "xargs/grep", just use the "-exec" option of the "find" command to execute "grep". Also, read line by line of the file matches from stdin when using "ls -lath".
That will spawn a new grep command for every file. The original command using xargs is much more efficient.
participants (6)
-
Bruce Kingsbury -
Cameron Rangeley -
Craig Box -
John -
Meeting Reminder Bot -
Peter Reutemann