MULTIDUMP(1)
okay so bestie, welcome to the MULTIDUMP(1) era β this page is from the General Commands Manual, and it's all about multidump, lowkey a multitasking icon. π
π NAME π
multidump β run multiple rtpdumps simultaneously. Periodt. β¨
β¨ SYNOPSIS β¨
multidump [-F format] [-t minutes] [-x bytes] basename [address]/port [...]
π¦ DESCRIPTION π¦
okay so multidump runs multiple rtpdump(1) sessions simultaneously. For every [address]/port, one rtpdump(1) process is started accordingly. Literally one per thing. π«Ά
The dumps are stored in basename.*, numbered from basename.1 increasingly β so basename.1, basename.2, and so on, you get the vibe. π
The -F, -t, and -x flags, if present, are passed to every rtpdump(1) process. No gatekeeping:
-Fformat β if present, gets passed to everyrtpdump(1)process. π-tminutes β if present, gets passed to everyrtpdump(1)process, and it also unlocks the waiting behavior below. β³-xbytes β if present, gets passed to everyrtpdump(1)process too. π¦
If the -t flag is used, multidump will wait for all the rtpdump(1) processes to finish. Otherwise, multidump will need to be killed with a signal β and in that case, it kills the running processes as well.
β οΈ no -t? then it's giving βgotta signal it to stop,β and it takes the running processes down with it. not a drill, bestie. π
π SEE ALSO π
okay bye bestie β this MULTIDUMP(1) page came from Debian, dated December 8, 2017. mwah π
π¦ where this page comes from
- nixos 26.05: rtptools 1.22
- nixpkgs unstable: rtptools 1.22
- π the page's license: BSD-3-Clause
- (c) 1998-2018 by Columbia University; all rights reserved
- (c) 2017-2018 by Jan Stary <hans@stare.cz>
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms