udpxrec(1)
π udpxrec β a programmable multicast traffic recording utility π
okay bestie, welcome to udpxrec(1), the manual page for the little program that saves a slice of multicast network traffic straight to disk π
β¨ SYNOPSIS β¨
udpxrec [-v] [-b <begin_time>] [-e <end_time>] [-M <maxfilesize>] [-p
<pidfile>] [-B <bufsizeK>] [-n <nice_incr>] [-u <seconds_to_wait>] [-m
<mcast_ifc_addr>] [-l <logfile>] [-s <ssm_source_addr>] -c
<src_addr>:<port> <dstfile>
no cap, that's the whole shape of it π
πΈ DESCRIPTION πΈ
udpxrec is a utility that records β like, saves into a disk file β a segment of multicast network traffic. it's giving "grab this stream and keep it". and the amount of data that gets saved/recorded? you can specify it in length (KB) or in duration (seconds). both. either. your call, queen π
π OPTIONS π
udpxrec accepts the following options:
-c <src_addr>:<port>β the Channel, bestie. i.e. the multicast address and port you're recording data from. iconic, mandatory, the main character of this whole operation.-s <ssm_source_addr>β optional SSM source address. optional!! but very useful if you know your source π¦-vβ enable verbose output. [default = disabled] β so by default she's quiet π€«-m <mcast_ifc_addr>β IPv4 address/interface of the (multicast) source. [default =0.0.0.0] π-l <logfile>β log output to a file. [default =stderr] β yeah, by default the logs just vibe out to stderr π-n <nice_incr>β nice value increment. [default =0] β polite little process, not asking for more priority than she needs π-B <sizeK>β buffer size for inbound (multicast) data. accepted vibes are like65536,32Kb,1Mb. [default =2048bytes] β¨-R <msgs>β maximum number of messages to buffer. (-1= all) [default =1] β lowkey the "hoard everything" switch π-b <begin_time>β begin recording at[+]dd:hh24:mi.ss, where a+signifies relative timing (in N hours/min/sec). so like, when do we start, bestie β°-e <endtime>β stop recording at[+]dd:hh24:mi.ss, where a+signifies relative timing (in N hours/min/sec). and when do we stop π-M <maxfilesize>β maximum size of the destination file. she will not grow past this, periodt π-p <pidfile>β pidfile for this process. MUST be specified if daemon π¨ like, not optional, not negotiable, mandatory.-u <seconds_to_wait>β seconds to wait before updating you on how long till recording starts. the "are we there yet" interval π«Ά
π heads up: -R shows up in the OPTIONS list above but she is not in the SYNOPSIS. i don't make the rules, i just report them faithfully.
π§ EXAMPLES π§
udpxrec -b 15:45.00 -e +2:00.00 -M 1.5Gb -n 2 -B 64K -s 87.141.215.251
-c 224.0.11.31:5050 /opt/video/tv5.mpg
let me translate this absolute slay of a command line, bestie:
begin recording multicast channel 224.0.11.31:5050 from source address 87.141.215.251 at 15:45 today, finish recording in two hours or if the destination file size goes >= 1.5 Gb β whichever comes first, no cap. also: set the socket buffer to 64Kb, increment the nice value by 2, and write the captured video to /opt/video/tv5.mpg π¬π₯
π AUTHORS π
Pavel V. Cherenkov and all the good people who submitted patches or otherwise contributed to the project. we love a collaborative queen ππ«Ά
π SEE ALSO π
udpxy(1)β go read her too, iykyk β¨
and that's a wrap!! this page is from Version 1.0, dated November 18, 2012, brought to you by the udpxrec(1) manual. stay recording, stay slaying π
ππ
π¦ where this page comes from
- fedora 43: udpxy 1.0.25.1-7.fc43 Β· GPL-3.0-or-later
- fedora 44: udpxy 1.0.25.1-8.fc44 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms