EVTINFO(1)
π evtinfo β the manual, but make it slay π
okay bestie, welcome to evtinfo(), a LOCAL manual page, and literally your new fave little detective for Windows Event Log (EVT) files. sit down, grab a strawberry drink π, and let's get into it.
β¨ NAME β¨
evtinfo β figures out the tea about a Windows Event Log (EVT). like, what even is in there. π
π¦ SYNOPSIS π¦
evtinfo [-c codepage] [-hvV] source
that's it. that's the whole vibe. one source, a couple optional flags, done. π
πΈ DESCRIPTION πΈ
evtinfo is a utility to determine information about a Windows Event Log (EVT). no cap, that's its whole job and it ate. π
it's part of the libevt package, bestie. and libevt is a library to access the Windows Event Log (EVT) format. so like, evtinfo is the cute little front-end friend of a much bigger library situation. iykyk.
source is the source file. like, the actual EVT file you want the info about. hand it over. π«Ά
The options are as follows:
-c codepageβ specify the codepage of ASCII strings. your choices are literally:ascii,windows-874,windows-932,windows-936,windows-949,windows-950,windows-1250,windows-1251,windows-1252(default, if you don't say anything),windows-1253,windows-1254,windows-1255,windows-1256,windows-1257orwindows-1258. pick your fighter. π-hβ shows this help. it's giving "help me help you". π-vβ verbose output to stderr. more words, more drama, all to stderr. π₯-Vβ print version. for when you gotta know exactly which one you're dealing with. β
π ENVIRONMENT π
None. nothing. zero. the environment said "not me". π
π§ FILES π§
None either. empty. a whole lotta nothing. we love a low-maintenance icon. β¨
π EXAMPLES π
okay here's the moment you've been waiting for. run it like this:
# evtinfo AppEvent.Evt
and you get back:
evtinfo 20120624
Windows Event Log (EVT) information:
Version : 1.1
Number of records : 19
Number of recovered records : 0
Log type : Application
Flags:
Should be archived
look at all that info. version 1.1. 19 records. 0 recovered records. log type Application. and the flags are saying "Should be archived". obsessed. ππ
π©· DIAGNOSTICS π©·
Errors, verbose and debug output are printed to stderr when verbose output -v is enabled. but β and this is the important part bestie β verbose and debug output are only printed when enabled at compilation. so if you didn't build it that way, no amount of -v is gonna manifest it. manifesting only works if you compiled it in. π§ββοΈ
π BUGS π
found a bug? don't be shy, please report bugs of any kind to <joachim.metz@gmail.com> or on the project website: https://github.com/libyal/libevt/. they wanna know. fr fr. π
π AUTHOR π
These man pages were written by Joachim Metz. iconic behavior, honestly. π
π COPYRIGHT π
Copyright (C) 2011-2020, Joachim Metz <joachim.metz@gmail.com>. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. read that again, bestie β no warranty. none. not even the implied ones. it's giving "you're on your own but legally". π
π SEE ALSO π
and that's the whole page, bestie! π¦ this came to you from libevt, dated April 13, 2019. go forth and evtinfo responsibly. periodt. πβ¨π
π¦ where this page comes from
- debian bookworm: libevt-utils 20200926-1+b2 Β· LGPL-3.0-or-later
- debian trixie: libevt-utils 20200926-2 Β· LGPL-3.0-or-later
- ubuntu jammy: libevt-utils 20200926-1build1 Β· LGPL-3.0-or-later
- ubuntu noble: libevt-utils 20200926-1.1build1 Β· LGPL-3.0-or-later
- ubuntu questing: libevt-utils 20200926-2
- ubuntu resolute: libevt-utils 20200926-2build1 Β· LGPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms