BOOTTRACE(8)

🫶 BOOTTRACE(8) 🫶

okay so hi bestie 💖 this is the System Manager's Manual page for boottrace(8), and it's lowkey iconic: it's all about running a command and dropping trace receipts before and after. Welcome to the trace era ✨

🌸 NAME 🌸

boottrace — trace command execution with boottrace(4) 🦋

✨ SYNOPSIS ✨

boottrace utility [argument ...]

🦋 DESCRIPTION 🦋

The boottrace utility executes the specified utility, and it creates two boottrace(4) trace entries: one before the execution and one after it. That's the whole plot, no cap 💅

🌈 ENVIRONMENT 🌈

The PATH environment variable is used to locate the requested utility if the name contains no / characters — that's the condition, periodt 🎀

💀 EXIT STATUS 💀

• If utility was executed successfully, its exit status is returned. 🥳
• If utility was found but could not be executed, an exit status of 126 is returned. 😭
• If utility could not be found, an exit status of 127 is returned. 👻

🍓 EXAMPLES 🍓

Execute the dumpon(8) utility, logging the trace entries:

$ boottrace dumpon -z /dev/gpt/swap0

This will appear in the output of the kern.boottrace.log sysctl(8) node, and it's giving data:

       CPU      msecs    delta process     event                PID CPUtime IBlks OBlks
         0   63918567        0 kernel      sysinit 0x2100001      0    0.00     0     0
       [...]
         0   64076940   120605 boottrace   dumpon start        1602    0.00     0     0
         0   64076942        2 boottrace   dumpon done         1602    0.00     0     0

🫶 SEE ALSO 🫶

boottrace(4), rc.subr(8) — go read those too, bestie 💖

💖 cute sign-off: this page is from Debian, dated February 18, 2022, and it answers to BOOTTRACE(8) — mwah, slay, bye 💋