htdump(1)

🌸 htdump(1) — the general commands manual page, but make it cute 🌸

okay bestie, welcome to htdump 💖 this is a General Commands Manual entry and honestly? she's a whole vibe.

---

✨ NAME ✨

htdump — write out an ASCII-text version of the document database 🫶

---

✨ SYNOPSIS ✨

htdump [options]

---

✨ DESCRIPTION ✨

So htdump writes out an ASCII-text version of the document database, and it does it in the same form as the -t option of htdig. that's it, that's the girl. no cap. 💅

---

✨ OPTIONS ✨

• -a — Use alternate work files. this tells htdump to append .work to database files, which lets it operate on a second set of databases. lowkey iconic for keeping your stuff separate ✨
• -c configfile — Use the specified configfile instead of the default. pick your own adventure 🎀
• -v — Verbose mode. and ngl bestie? this doesn't have much effect 🙈

---

✨ File Formats ✨

💾 Document Database

Every single line in the file starts with the document id, followed by a list of fieldname : value separated by tabs. and the fields always appear in the order listed below — the order is the moment, don't fight it:

• u — URL 🔗
• t — Title
• a — State (0 = normal, 1 = not found, 2 = not indexed, 3 = obsolete) 👑
• m — Last modification time as reported by the server
• s — Size in bytes
• H — Excerpt
• h — Meta description
• l — Time of last retrieval
• L — Count of the links in the document (outgoing links) 📤
• b — Count of the links to the document (incoming links or backlinks) 📥
• c — HopCount of this document
• g — Signature of the document used for duplicate-detection 🕵️
• e — E-mail address to use for a notification message from htnotify 📧
• n — Date to send out a notification e-mail message
• S — Subject for a notification e-mail message
• d — The text of links pointing to this document. (e.g. <a href="docURL">description</a>)
• A — Anchors in the document (i.e. <A NAME=...)

💾 Word Database

okay so here's the tea: while htdump and htload don't deal with the word database directly, it's worth mentioning it here because you need to deal with it when copying the ASCII databases from one system to another. 👀

The initial word database produced by htdig is already in ASCII format, and a binary version of it is produced by htmerge, for use by htsearch. So, when you copy over the ASCII version of the document database produced by htdump, you need to copy over the wordlist as well, then run htload to make the binary document database on the target system, followed by running htmerge to make the word index. that's the whole pipeline bestie, respect it 🫶

Each line in the word list file starts with the word, followed by a list of fieldname : value separated by tabs. The fields always appear in the order listed below, with the last two being optional:

• i — Document ID
• l — Location of word in document (1 to 1000)
• w — Weight of word based on scoring factors
• c — Count of word's appearances in document, if more than 1
• a — Anchor number if word occurred after a named anchor

---

✨ FILES ✨

• /etc/htdig/htdig.conf — The default configuration file. 🎀
• /var/lib/htdig/db.docs — The default ASCII document database file. 📄
• /var/lib/htdig/db.wordlist — The default ASCII word database file. 📝

---

✨ SEE ALSO ✨

Please refer to the HTML pages (in the htdig-doc package) /usr/share/doc/htdig-doc/html/index.html and the manual pages htdig(1) , and htload(1) for a detailed description of ht://Dig and its commands. go read them, they ate 💅

---

✨ AUTHOR ✨

This manual page was written by Stijn de Bekker, based on the HTML documentation of ht://Dig. 👑

---

and that's a wrap bestie!! 🦋 this page is dated 15 October 2001 and it comes from htdump(1) — yeah the footer literally just says that again, she's consistent. periodt 💖✨