SC_WARTS2TEXT(1)

πŸ’– SC_WARTS2TEXT πŸ’–

okay bestie, so this is sc_warts2text, a lil' utility from the General Commands Manual section (section 1, the classics ✨). she's not fancy, she's not complicated, she just wants to show you what's inside your warts files. and honestly? iconic of her. πŸŽ€


✨ NAME ✨

sc_warts2text β€” a simple dump of information contained in a warts file. that's it, that's the whole job, and she does it flawlessly πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

sc_warts2text [-d ip2descr-file] [file ...]

🌸 DESCRIPTION 🌸

so, sc_warts2text gives you a simple dump of the information contained in a sequence of warts files. yes, multiple, she can handle multiple. multitasking queen. πŸ‘‘

the output you get is literally the same as what you'd have gotten from scamper if you'd picked the text output option instead of the warts output option back when the data was collected. same vibes, different era, iykyk.

the options are as follows:

  • -d ip2descr-file β€” this one specifies the name of a file with IP-address, description mappings, one mapping per line. wanna see how that works? the examples section has you covered, bestie. go look. 🫢
⚠️ okay so REAL TALK for a sec because this part matters: while the output of sc_warts2text is structured and totally suitable for initial analyses of results, the format of the output is not suitable for automated parsing and analysis. and why? because the output of sc_warts2text will change over time with no regard to backwards compatibility. no cap. she said "i evolve, keep up." 😭 so if you're doing analyses of the contents of a warts file, do it properly with specialised programs which link against the scamper file API. periodt. πŸ’€

🌈 EXAMPLES 🌈

okay so say you run this command:

sc_warts2text file1.warts file2.warts

what happens? she will decode and print the contents of file1.warts, and then, right after, the contents of file2.warts. back to back, no interruptions. 🧚

now, say you run this one instead:

gzcat file1.warts.gz | sc_warts2text

this one will print the contents of the uncompressed file supplied on stdin. so you pipe it in, she dumps it out, everybody eats. πŸ“

and now my favorite part β€” the mapping glow-up. πŸ’– given a set of IP-address, description pairs in a file named mappings.txt:

192.0.2.1 "foo"
192.0.2.2 "bar"

then this command:

gzcat file1.warts.gz | sc_warts2text -d mappings.txt

will print the description associated with a given destination address before each result is presented. so you're not just staring at raw addresses, you're getting the name too. she said "let me introduce you." 😌✨


πŸ‘€ SEE ALSO πŸ‘€


🫢 AUTHORS 🫢

sc_warts2text was written by Matthew Luckie <mjl@luckie.org.nz>. absolute legend behavior, we stan. πŸ‘‘


and that's the whole page, bestie β€” this one ships as part of Debian, and this version is dated October 15, 2010. yes, she's been serving since 2010 and she has not missed a day. mwah. πŸ’‹πŸ’