#digitalsalon

March 22, 2013
[20:09:11] pilgrimish: leaves
[20:09:58] pilgrimish: joins
[20:47:30] pilgrimish: leaves
[21:07:21] pilgrimish: joins
[21:49:12] pilgrimish: leaves
[01:37:07] pilgrimish: joins
[01:44:58] pilgrimish: leaves
[02:34:49] pilgrimish: joins
[03:02:24] pilgrimish: leaves
[07:57:53] waltd3: joins
[09:03:36] thisgeek: joins
[09:29:54] waltd3: always wondered how to do this. finally found an easy way
[09:29:54] waltd3: http://stackoverflow.com/questions/4650026/how-do-i-grep-the-contents-of-files-returned-by-grep
[09:30:04] waltd3: grep -l foo $(grep -l error *.log)
[09:30:25] kenbolton: nice
[09:32:22] thisgeek: I guess this is different from using the recursive option, right?
[09:33:05] waltd3: i think so. recursive just searches subdirectories
[09:33:34] waltd3: this lets you filter files by one string. and then filter that subset of files again for a different string.
[09:34:47] waltd3: in my case, i was looking for all files that were accessing a certain server. and then i wanted to print out a unique id found in those files.
[09:45:13] thisgeek: Cool. Thank for posting.
[10:17:58] pilgrimish: joins
[10:23:39] pilgrimish: leaves
[10:24:12] pilgrimish: joins
[10:47:32] kenbolton: leaves
[11:04:46] kenbolton: joins
[11:58:24] pilgrimish: leaves
[12:07:47] pilgrimish: joins
[13:28:14] pilgrimish: leaves
[13:33:01] pilgrimish: joins
[13:45:24] kenbolton: leaves
[13:54:38] pilgrimish: leaves
[13:55:55] kenbolton: joins
[14:04:27] pilgrimish: joins
[14:11:41] pilgrimish: leaves
[15:31:29] kenbolton: leaves
[15:38:01] kenbolton: joins
[15:44:38] kenbolton: leaves
[16:00:30] pilgrimish: joins
[16:40:24] kenbolton: joins
[16:43:54] pilgrimish: leaves
[16:47:37] pilgrimish: joins
[17:25:07] thisgeek: leaves
[17:36:00] pilgrimish: leaves
[17:50:35] pilgrimish: joins
[18:51:54] pilgrimish: leaves
[18:54:57] pilgrimish: joins