BFDJSON(8)

πŸ“¦
version 15.0.3 Β· 2 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, debian trixie, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– BFDJSON β€” the Bacula JSON config dumper, bestie edition πŸ’–

okay so this is bfdjson from section 8 of the manual (that's the Network backup, utilities corner of the man page universe, iykyk). pull up a chair, grab a boba, and let's get into it πŸ§‹βœ¨


🌸 NAME 🌸

bfdjson β€” literally Bacula's JSON configuration export tool. that's the whole vibe. it exports. it's JSON. it's iconic.


✨ SYNOPSIS ✨

bfdjson [options]

that's it. no positional args, no drama, just options. she's low maintenance πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

so this manual page documents briefly the bfdjson command. briefly!! we're keeping it brief!! (well. as brief as a girl who loves her flags can be πŸ™ˆ)

it's a simple program that will allow you to dump the Bacula File Daemon configuration in JSON format. that's the whole main character arc. you point it at a config, it hands you JSON, you go slay. periodt πŸŽ€


πŸ‘‘ OPTIONS πŸ‘‘

a summary of options is included below. and when i say summary i mean the full list, because we do not gatekeep on this account 🫢

  • -? β€” shows the version and usage of the program. the "hi bestie, who am i" flag 🌈
  • -d nn β€” sets the debug level to nn. turn the volume up on the internal monologue πŸ”Š
  • -dt β€” prints a timestamp in the debug output. so you know when things were being dramatic ⏰
  • -r <res> β€” get resource type. you're asking for a specific kind of resource here πŸ“
  • -n <name> β€” get resource name. now you're getting specific about which one, love that for you πŸ’œ
  • -l <dirs> β€” get only directives matching dirs (use with -r). yes bestie, it's a combo move β€” pair it with -r or it's giving nothing πŸ”₯
  • -D β€” get only data. just the data. nothing but the data. the data is the moment πŸ’€
  • -R β€” do not apply JobDefs to Job. hands off the JobDefs, she said no πŸ’…
  • -c <file> β€” set configuration file to file. tell her which file to read, she's not a mind reader ✨
  • -d <nn> β€” set debug level to <nn>. (yep, she's listed twice in the original β€” we don't erase history in this house, we honour it πŸ™ˆ)
  • -dt β€” print timestamp in debug output. (also listed twice. the original said it, so i said it. no cap 🧚)
  • -t β€” read the configuration and exit. in and out, no lingering, respect πŸŽ€
  • -s β€” output in show text format. different format, same energy 🌸
  • -v β€” verbose user messages. she will talk to you. let her πŸ—£οΈ
heads up bestie: -d nn and -d <nn> both appear in the original option list, and -dt shows up twice too. that's not me being chaotic (well, not only me) β€” that's literally what the page says, and i'm not about to edit the source material. keeping every line, always πŸ’–

πŸŽ€ AUTHOR πŸŽ€

this manual page was written by Eric Bollengier <eric@baculasystems.com>. and this man page document is released under the BSD 2-Clause license. iconic of them, honestly ⭐


and that's the whole page, bestie!! written by Eric Bollengier, dated 12 September 2023, living in section BFDJSON(8) forever. go dump some config, you absolute legend πŸ¦‹πŸ’–βœ¨

πŸ“¦ where this page comes from