Search results matching tag 'FS input format'

RE: Directory Tree

LogParser User : José Gisbert — Fri, 22 Jun 2007 17:44:00 GMT

More Easy:
C:\>Tree /A > My_C_Tree.txt
;o)

LASTACCESSTIME showing wrong date

LogParser User : Vizo — Wed, 06 Jun 2007 16:01:00 GMT

Hello guys:

Using logparser to generate a report so I can clean up my file server. For some reason logparser is giving me a year of 1969 on some files. running my query on a windows 2003 server against a share on windows 2000 if that helps.

Thanks

vizo

RE: Supress error when no matching files?

LogParser User : David Manley — Sat, 19 May 2007 00:12:00 GMT

Thanks Daniel. Your reply got me thinking along a suitable track.

I was averse to having a "token" file that is known to exist on the basis that one day there may be a need to include the given token file in the results but a variation on your suggestion works for me. Namely, to include within the "from" list a known directory (i.e. '.') and then exclude directories via a check on the attributes, such as:

"f:\Program Files\Log Parser 2.2\LogParser.exe" -i:FS "SELECT path FROM '%WINDIR%\*.xyz', '.' WHERE substr(attributes,0, 1) <> 'D'"

Statistics:
-----------
Elements processed: 2
Elements output: 0
Execution time: 0.78 seconds

F:\temp>echo %errorlevel%
0

Thanks for your response.

David

RE: Supress error when no matching files?

LogParser User : DEinspanjer — Fri, 18 May 2007 11:16:00 GMT

Hrm. Only thing I can think of off the top of my head is to have a dummy file that is always there.
Something like this worked for me:

"C:\Program Files\Log Parser 2.2\LogParser.exe" -i:FS "SELECT path FROM C:\tmp\scores.txt, 'C:\tmp\*.xyz' WHERE Path <> 'C:\tmp\scores.txt'"
Statistics:                                                                                                            
-----------                                                                                                            
Elements processed: 1                                                                                                  
Elements output:    0                                                                                                  
Execution time:     0.08 seconds

Supress error when no matching files?

LogParser User : David Manley — Fri, 18 May 2007 08:29:00 GMT

When the input format is file system, if no files match the pattern, LogParser considers this an error. This is demonstable by the following:

"C:\Program Files\Log Parser 2.2\LogParser.exe" -i:FS "SELECT path FROM '%WINDIR%\*.xyz'"

Task aborted.
Cannot open <from-entity>: Cannot find any file or folder matching
"C:\WINDOWS\*.xyz"

Statistics:
-----------
Elements processed: 0
Elements output: 0
Execution time: 0.67 seconds

F:\temp>echo %errorlevel%
2

Does anyone know of a way to get LogParser to not consider the absence of any matching files as being an error? (Note the example is for illustrative purposes only, so that it can be run by anyone, rather than the actual query that is to be run).

Thanks.

David

RE: Compare fs listing against IIS listing

LogParser User : DEinspanjer — Fri, 26 Jan 2007 17:30:00 GMT

by "documented" I mean I made a post where I gave an example of using the TPL output format to create a SQL query file that is then run by LP. It's in the General Discussion forums

RE: Compare fs listing against IIS listing

LogParser User : justSteve — Fri, 26 Jan 2007 13:12:00 GMT

[QUOTE User="LogParser User : justSteve"]Quote: I can't say as there is actually a drop dead easy way. Let me see if I understand exactly what you want. You want to run an LP query against the IIS log files to find out "active" pages, then you wa...[/QUOTE]
Thanks for the quick reply...given this is a one off situation i'm probably best off importing to a couple sql tables. But it would be interesting to see real-world TPL samples.

RE: Compare fs listing against IIS listing

LogParser User : DEinspanjer — Fri, 26 Jan 2007 13:01:00 GMT

I can't say as there is actually a drop dead easy way.
Let me see if I understand exactly what you want.
You want to run an LP query against the IIS log files to find out "active" pages, then you want to run another LP query against the FS input format to find files that are not in that "active" pages list?

Because of the limitations in the current version of LP of not being about to do subqueries against different input formats (e.g. can't query FROM FS with a subquery that queries FROM IIS), you'll have to do some magic to get the list of active pages into your second query.

I'd suggest using the TPL query generation method I documented in the General Discussion forum a while back. The first IIS query will output a list of the file names into a TPL format that is actually writing a new query that contains a where clause along the lines of:
WHERE FileName NOT IN (
'fn1.asp';
'fn2.asp';
'fn3.asp';
)

And then you run LP on that generated query.

Compare fs listing against IIS listing

LogParser User : justSteve — Fri, 26 Jan 2007 12:29:00 GMT

I'm inheriting a very old IIS box...it's been thru a number of different masters and has lots of files no longer in use intermixed with active files.

I can produce a listing of pages served by IIS and files found via FS...I bet there's a drop dead easy way to do something like 'select name where [FSFiles] NOT IN [IISFiles] directly instead of importing both lists to tables and running from there.

I'll bet a beer there's a drop dead easy way.

[thankx for the tool...already owe the auther a 6pack.]

--steve...

RE: View the size,name and Path of a directory

LogParser User : Jeff — Fri, 19 Jan 2007 16:26:00 GMT

My implementation is slightly different:

select
extract_token(path,add(1,strcnt('%CD%','\\')),'\\') as dir,
sum(size) as sumsize

from
'%CD%\*'
where
Name not in ('.';'..')

group by
dir

order by
sumsize
desc

Note, if you save it as a file you have to call it like:

logparser -i:fs file:getdiskspace.sql?CD=%CD%

(%CD% isn't a real environment variable - so Log Parser can't find it)