OBUS-INTROSPECT(1)

πŸ’… NAME πŸ’…

obus-introspect β€” a D-Bus introspecter, aka the girl who walks up to a D-Bus service and asks it to spill everything about itself ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

obus-intrpsoect [ options ] destination path
bestie the command name up there is spelled exactly how the original page spells it, ok? i don't make the rules, i just keep them character for character 🫢

🌸 DESCRIPTION 🌸

okay so obus-introspect lets you introspect a D-Bus service β€” like, you hand it a destination and a path, and it goes and finds out what's actually living there. no cap, it's giving private investigator but make it cute.

given a path, it can introspect recursively, like, all its children. and by default? it prints only all the interfaces it found. but it can also print all object paths together with the interfaces they implement, if you ask it nicely πŸ’–

so basically: default vibe = just the interfaces. extra vibe = objects + the interfaces they implement. you choose, queen.


✨ OPTIONS ✨

  • -rec β€” introspects recursively, like, all the sub-nodes instead of just the one at path. yes, all of them. it goes down the whole tree, main character energy 🧚
  • -session β€” the service is on the session bus. also this is the default, so if you don't say anything, this is what you get πŸŽ€
  • -system β€” the service is on the system bus. different bus, different vibe 🚌
  • -objects β€” lists objects with the interfaces they implement, instead of just listing interfaces. the fuller picture, the whole look πŸ‘‘
  • -help or --help β€” displays a short usage summary and then exits. it's literally just here to help a girl out 😭

πŸ‘‘ AUTHOR πŸ‘‘

JΓ©rΓ©mie Dimino <jeremie@dimino.org>


🌈 SEE ALSO 🌈

obus-dump(1), obus-binder(1).


and that's the whole page fr fr πŸ’œ this beauty came out of the General Commands Manual section, dated October 2009 β€” iconic behavior honestly, periodt ⭐