wcmgr(1)
β¨ wcmgr β Webalizer (DNS) Cache file Manager β¨
okay bestie, welcome to the wcmgr manual page, part of The Webalizer family π
πΈ NAME πΈ
wcmgr β the Webalizer (DNS) Cache file Manager π§
β¨ SYNOPSIS β¨
wcmgr [ option ... ] cache-file
π¦ DESCRIPTION π¦
okay so wcmgr is this little utility program that lets you mess with the DNS cache files that The Webalizer uses and makes. literally its whole thing π
so every single record in the cache file holds:
- an IP address (and it can be IPv4 or IPv6, she's versatile)
- a timestamp of when that entry got added to the cache
- a flag saying whether the record has a resolved name or not
- and then either the same IP address or a resolved host name
and the way you access all of these? by their IP address. that's the key, that's the whole vibe π
π RUNNING WCMGR π
so wcmgr was designed to be run straight from the Unix shell command line. why? because it makes it so easy to drop into shell scripts and other automated processes, periodt β¨
you must specify a valid DNS cache file, no skipping that part. the command line options though? those are optional, bestie. and if you give none at all, the default action is to just list the contents of the cache file you specified. cute, simple, done π«Ά
π COMMAND LINE OPTIONS π
so you pick different functions by throwing in one or more of these. and if you give literally no options? the default is to display the contents of the cache file to the screen (stdout). no notes πΊ
-hβ show you every single available command line option, then exit. it's giving "help me help you" π-vβ be verbose. say more. spill β-Vβ display the program version and exit. and if you also turn on verbose mode (like-vV), you get extra program specific info too, which is lowkey useful when you're submitting bug reports π-aaddress[-nhostname] [-t0]β add a new record to the cache file. the IP address gets added using the current time as the timestamp, with a resolved name of hostname. if you specify-t0, that record is considered permanent β it will not be removed during a purge, and it won't expire. ever. main character energy π. and if you don't give a hostname with the-noption, then the address is used instead and the record gets flagged as unresolved.-cβ create a new cache file. if you use it all by itself, you get a brand new, empty cache file. if you use it with the import option, a new cache file gets created before the data gets imported. β οΈ heads up: you get an error if the file cache-file already exists. no overwriting, she said no π«-daddress β delete a record from the cache file using the specified address. bye bestie π-faddress β find address in the cache file and show you the info. you get a single line similar to what-lproduces, unless verbose mode is on, in which case you get a much more detailed listing. glow up β¨-iname[-c]β import data into the cache file from the file name. that import file must be a valid tab delimited text file, like the kind the export option creates. if the imported data has records that are already in the cache file, the imported data overwrites them. the cache file has to already exist unless you specify-c, in which case a brand new cache file gets created for the imported data π±-lβ list the contents of the cache file. this is the default action of the program, so you don't necessarily have to say it out loud. and if verbose mode is enabled, you also get a report title, column headers and summary totals π₯°-pnum β purge the cache file of entries older than num days. if you don't give a num, the default of7days is used. if verbose mode is enabled, every single purged record gets printed, plus the total number of purged records. cleansing ritual π§Ή-s[-tnum]β display cache file information/statistics. if you specify a TTL value (in days) with the-toption, that's what gets used to calculate how many records are older than num days. otherwise the default value of7days is used π-nname β specify the name to use as the resolved hostname when adding records to the cache. naming rights, slay π-tnum β Time to live (TTL) value. if you use it with the-p(purge) option, it says how many days a record stays valid. any record older than num days is considered expired and gets purged. if you use it with the-a(add) option, a zero value makes the record permanent β³-xname β export data from a cache file out to a tab delimited text file named name. β οΈ if that text file name already exists, it gets overwritten. no warning, just gone π
π BUGS π
please report bugs to the author. they want to know, fr fr π
Β©οΈ COPYRIGHT Β©οΈ
Copyright (C) 1997-2013 by Bradford L. Barrett. Distributed under the GNU GPL. see the files "COPYING" and "Copyright", supplied with all distributions, for additional information π
π AUTHOR π
Bradford L. Barrett <brad at mrunix dot net> π
and that's the whole page bestie, you ate that π this was Version 1.00, dated 12-Jul-2008, from The Webalizer β go forth and manage those caches, iykyk πβ¨π¦
π¦ where this page comes from
- alpine 3.24: webalizer-doc 2.23.08-r9 Β· GPL-2.0-or-later
- debian bookworm: webalizer 2.23.08-3.3 Β· GPL-2.0-or-later
- fedora 43: webalizer 2.23_08-29.fc43 Β· GPL-2.0-or-later
- fedora 44: webalizer 2.23_08-30.fc44 Β· GPL-2.0-or-later
- nixos 26.05: webalizer 2.23.08
- nixpkgs unstable: webalizer 2.23.08
- opensuse-leap 16.0: webalizer 2.23-bp160.1.10 Β· GPL-2.0-or-later
- opensuse-leap 16.0: webalizer 2.23-bp160.1.10 Β· GPL-2.0-or-later
- opensuse-leap 16.0: webalizer 2.23-bp160.1.10 Β· GPL-2.0-or-later
- opensuse-leap 16.0: webalizer 2.23-bp160.1.10 Β· GPL-2.0-or-later
- ubuntu jammy: webalizer 2.23.08-3.2 Β· GPL-2.0-or-later
- ubuntu noble: webalizer 2.23.08-3.3build2 Β· GPL-2.0-or-later
- ubuntu questing: webalizer 2.23.08-3.3build2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms