OPARCHIVE(1)

πŸ“¦
version 1.4.0 Β· 5 versions
, in opensuse-leap 16.0

✨ OPARCHIVE(1) ✨

okay bestie, so this is oparchive β€” the Unix manual page that literally saves your whole profile vibe for later πŸ’…


🌸 NAME 🌸

oparchive β€” make an archive of your oprofile data so you can analyze it offline later πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

oparchive [ options ] [profile specification] -o [directory]

πŸ’– DESCRIPTION πŸ’–

okay so the oparchive utility is that girl for collecting profile data on a "target" system so you can do offline analysis later on a totally different ("host") machine. lowkey iconic 🫢

oparchive creates a directory all stocked up with executables, libraries, debuginfo files, and oprofile sample files. then you can just tar it up and move it to another machine to analyze it there β€” no further use of the target machine needed, periodt ✨

when you wanna use opreport and other post-profiling tools against archived data, you have to use the archive:<archived-dir> specification. see oprofile(1) for the whole how-to on writing profile specifications, iykyk πŸ“

there's a complete description of offline analysis in the chapter called Analyzing profile data on another system (oparchive) of the OProfile user manual. (the user manual URL is in the "SEE ALSO" section down below πŸ‘‡)


πŸŽ€ OPTIONS πŸŽ€

  • --help / -? / --usage β€” shows the help message. the classic "wait what does this do" moment πŸ’€
  • --version / -v β€” shows the version. gotta know what you're working with ✨
  • --verbose / -V [options] β€” gives you verbose debugging output. very "tell me everything" energy πŸ”
  • --session-dir=dir_path β€” uses the sample database from the specified directory dir_path instead of the default location. if --session-dir isn't specified, then oparchive searches for samples in <current_dir>/oprofile_data first. and if that directory doesn't exist, the standard session-dir of /var/lib/oprofile is used πŸ“
  • --image-path / -p [paths] β€” a comma-separated list of additional paths to search for binaries. this is needed to find modules in kernels 2.6 and upwards 🧚
  • --root / -R [path] β€” a path to a filesystem to search for additional binaries 🌈
  • --output-directory / -o [directory] β€” output to the given directory. there is no default β€” this one must be specified, no pressure or anything πŸ’…
bestie fr fr: -o has no default, so if you forget it, you're not going anywhere 😭
  • --exclude-dependent / -x β€” do not include application-specific images for libraries, kernel modules and the kernel. this option only makes sense if the profile session used --separate πŸ‘‘
  • --list-files / -l β€” only lists the files that would be archived, doesn't copy them. very "look but don't touch" vibes πŸ™ˆ

⭐ ENVIRONMENT ⭐

no special environment variables are recognized by oparchive. that's it, that's the whole section πŸ“


🧚 FILES 🧚

  • <session_dir>/samples β€” the location of the generated sample files πŸ’œ

πŸ”₯ VERSION πŸ”₯

this man page is current for oprofile-1.4.0 ⭐


🌈 SEE ALSO 🌈


πŸ’€ real talk: this page is from the 4th Berkeley Distribution, dated Thu 28 September 2023, and it's current for oprofile-1.4.0 β€” so go forth and archive responsibly, bestie 🫢✨
πŸ“¦ where this page comes from