REMUNGE(1)

๐Ÿ’– REMUNGE(1) โ€” the MUNGE creds-per-second glow-up ๐Ÿ’–

okay bestie, real talk: this is remunge from the MUNGE Uid 'N' Gid Emporium, and it's literally the vibe-check tool for how fast MUNGE can make credentials. sit down, hydrate, let's go ๐Ÿซถ


โœจ NAME โœจ

remunge โ€” MUNGE credential benchmark ๐ŸŒธ


๐ŸŽ€ SYNOPSIS ๐ŸŽ€

remunge [OPTION]...

like, that's it. options only. no positional args, no drama ๐Ÿ’…


๐Ÿฆ‹ DESCRIPTION ๐Ÿฆ‹

So remunge benchmarks how fast MUNGE is performing. A benchmark keeps running for the duration you picked, or until it's chewed through the number of credentials you picked โ€” whichever comes first. iconic race, honestly.

When it wraps up, it writes the number of credentials processed per second to stdout. that's the number. the moment. the main character stat ๐Ÿ‘‘

By default? Credentials get encoded for one second using a single thread. one thread. one second. minimal effort, maximal results, we love a low-effort queen ๐Ÿ’œ


๐Ÿ’… OPTIONS ๐Ÿ’…

  • -h, --help โ€” shows you a summary of all the command-line options. your little map ๐Ÿ—บ๏ธ
  • -L, --license โ€” shows the license info. legal girlies, this one's for you ๐Ÿ“œ
  • -V, --version โ€” shows version info. โœจ
  • -q, --quiet โ€” shows only the creds/sec numeric result, nothing else. lowkey obsessed with this one because it's perfect for producing input files for ministat. number only, no yapping ๐Ÿคซ
  • -c, --cipher string โ€” pick your cipher type, either by name or by number ๐Ÿ”
  • -C, --list-ciphers โ€” displays a list of supported cipher types. window shopping ๐Ÿ›๏ธ
  • -m, --mac string โ€” pick your MAC type, either by name or by number ๐Ÿงฎ
  • -M, --list-macs โ€” displays a list of supported MAC types.
  • -z, --zip string โ€” pick your compression type, either by name or by number ๐Ÿ—œ๏ธ
  • -Z, --list-zips โ€” displays a list of supported compression types.
  • -e, --encode โ€” encodes (but does not decode) each credential. and the way it skips the decode step means the credential is not stored in the replay cache. no receipts, no trace, gone girl ๐Ÿ’€
  • -d, --decode โ€” encodes and decodes each credential. the full journey, both directions ๐Ÿšถโ™€๏ธ๐Ÿšถ
  • -l, --length bytes โ€” sets an arbitrary payload length, in bytes. the integer can be followed by a single-character modifier: k=kilobytes, m=megabytes, g=gigabytes; K=kibibytes, M=mebibytes, G=gibibytes. yes the capital letters mean something different, do not come for me ๐Ÿ“
  • -u, --restrict-uid uid โ€” sets the user name or UID allowed to decode the credential. this gets matched against the effective user ID of the process requesting that credential decode ๐Ÿ”’
  • -g, --restrict-gid gid โ€” sets the group name or GID allowed to decode the credential. this gets matched against the effective group ID of the process requesting the credential decode, plus every supplementary group that the effective user ID of that process is a member of. group chat access control fr fr ๐Ÿ‘ฏ
  • -t, --ttl seconds โ€” sets the time-to-live in seconds. this controls how long the credential stays valid once it's been encoded. 0 selects the default TTL. -1 selects the maximum allowed TTL. choose your own adventure โณ
  • -S, --socket path โ€” sets the local socket used for connecting with munged. ๐Ÿ“ž
  • -D, --duration seconds โ€” sets the test duration in seconds. default duration is one second. -1 selects the maximum duration. the integer can be followed by a single-character modifier: s=seconds, m=minutes, h=hours, d=days. โฑ๏ธ
  • -N, --num-creds integer โ€” sets the number of credentials to generate. the integer can be followed by a single-character modifier: k=kilobytes, m=megabytes, g=gigabytes; K=kibibytes, M=mebibytes, G=gibibytes. yes, those are the modifiers listed for credential counts, we're just reporting the facts bestie ๐Ÿ“
  • -T, --num-threads integer โ€” sets the number of threads to spawn for processing credentials. bring the whole squad ๐Ÿงš
  • -W, --warn-time seconds โ€” sets the maximum number of seconds to allow for a given munge_encode() or munge_decode() operation before issuing a warning. it's giving "hey, we noticed" โš ๏ธ

๐ŸŒˆ EXIT STATUS ๐ŸŒˆ

remunge returns a zero exit code if the benchmark completes. slay โœ…

On error, it prints an error message to stderr and returns a non-zero exit code. not slay, but informative ๐Ÿ˜ญ


๐Ÿ’œ AUTHOR ๐Ÿ’œ

Chris Dunlap <cdunlap@llnl.gov> โ€” the actual legend who wrote this ๐Ÿ‘‘


Copyright (C) 2007-2025 Lawrence Livermore National Security, LLC. Copyright (C) 2002-2007 The Regents of the University of California.

MUNGE is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

Additionally for the MUNGE library (libmunge), you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

bestie, this is the legal fine print and it matters. free software, GPL/LGPL, version 3 or later, your choice. no cap ๐Ÿซถ

๐Ÿ‘€ SEE ALSO ๐Ÿ‘€

munge(1), unmunge(1), munge(3), munge_ctx(3), munge_enum(3), munge(7), munged(8), mungekey(8).

https://github.com/dun/munge


and that's the whole page, bestie ๐Ÿ’– this one came from munge-0.5.18, dated 2026-02-10, and it's the REMUNGE(1) manual page โ€” go benchmark something and tell me your creds/sec, i'll be so proud of you ๐ŸŽ€โœจ

๐Ÿ“ฆ where this page comes from