SC_ATTACH(1)

💖 SC_ATTACH(1) 💖

okay bestie so this is the manual for sc_attach from the General Commands Manual section — yes, section 1, we love a user command ✨

---

✨ NAME ✨

sc_attach — simple scamper driver. that's it, that's the name, no cap 💅

---

🦋 SYNOPSIS 🦋

sc_attach [-?dDv] [-c command] [-i infile] [-o outfile] [-O options]
          [-p [ip:]port] [-P priority] [-R unix-domain] [-U unix-domain]

---

🌸 DESCRIPTION 🌸

so the way sc_attach works is: it lets you connect to a scamper(1) instance that's already running, get a whole set of commands (defined in a file) executed, and then have the output written into a single file — in warts format. iconic behavior honestly. 🎀

the options are as follows:

• -? — prints a list of command line options plus a synopsis of each. your little cheat sheet, love that for you 📝
• -d — prints each command sent to scamper(1) over on stderr. so you can watch the tea being spilled in real time 👀
• -D — causes sc_attach to operate as a daemon. main character energy, running in the background 💅
• -v — prints the current revision of sc_attach and then exits. bye bestie 👋
• -c command — specifies the scamper(1) command to prepend to each address in the input file. like, every address gets this command glued on the front 🫶
• -i infile — specifies the name of the input file, which consists of a sequence of scamper(1) commands or addresses (with the -c option), one per line. and if you pass '-', commands are read from stdin instead 😌
• -o outfile — specifies the name of the output file to be written. the output file will use the warts format. and if you pass '-', output gets sent to stdout 🌈
• -O options — lets the behavior of sc_attach be further tailored. the current choices for this option are:
  • random: shuffle the input commands randomly. chaos, but make it ✨intentional✨
  • impatient: send commands to scamper without waiting for scamper to ask for them. no thoughts, just send 🔥
• -p [ip:]port — specifies the IP address and port where a scamper(1) is accepting control socket connections. if an IP address is not specified, sc_attach connects to the specified port on the local host 🏠
• -P priority — specifies the mixing priority scamper(1) should assign to the source 🎚️
• -R unix-domain — specifies the unix domain socket on the local host where a remote scamper(1) instance is accepting commands 🌍
• -U unix-domain — specifies the unix domain socket on the local host where a local scamper(1) instance is accepting commands 💻

---

🎀 EXAMPLES 🎀

so say you've got a set of commands in a file named infile.txt:

tbit -M 1280 -u 'http://www.example.com/' 2620:0:2d0:200::10
trace -P udp-paris -M 192.0.2.1
ping -P icmp-echo 192.0.32.10

and a scamper(1) daemon listening on port 31337, then these commands can be executed using:

sc_attach -i infile.txt -o outfile.warts -p 31337

now, say you've got a set of addresses in a file named infile2.txt:

2620:0:2d0:200::10
192.0.2.1
192.0.32.10

these addresses can be pinged with sc_attach operating as a daemon with:

sc_attach -D -c 'ping' -i infile2.txt -o outfile2.warts -p 31337

slay. 💅

---

👑 SEE ALSO 👑

scamper(1), sc_wartsdump(1), sc_warts2json(1)

go read those too bestie, iykyk 🦋

---

💜 AUTHORS 💜

sc_attach was written by Matthew Luckie <mjl@luckie.org.nz>. absolute legend, we stan 🫶

---

and that's the whole vibe check, bestie — this page came to you from Debian, dated February 2, 2016. periodt. 💖✨