[logs] Collect /var/lib/rsyslog/ directory listings

[abetkike]

Add directory listings for /var/lib/rsyslog/ to help diagnose
rsyslog state file issues and verify SELinux contexts on the
path hierarchy. Commands fail gracefully when rsyslog is not
installed or uses a non-default WorkDirectory.

Collects:

• ls -ldZ /var/ /var/lib/ /var/lib/rsyslog/ — path hierarchy with SELinux labels
• ls -lZ /var/lib/rsyslog/ — directory contents with SELinux labels

---

• Is the commit message split over multiple lines and hard-wrapped at 72 characters?
• Is the subject and message clear and concise?
• Does the subject start with [plugin_name] if submitting a plugin patch or a [section_name] if part of the core sosreport code?
• Does the commit contain a Signed-off-by: First Lastname email@example.com?
• Are any related Issues or existing PRs properly referenced via a Closes (Issue) or Resolved (PR) line?
• Are all passwords or private data gathered by this PR obfuscated?

[packit-as-a-service]

Congratulations! One of the builds has completed. 🍾

You can install the built RPMs by following these steps:

• sudo dnf install -y 'dnf*-command(copr)'
• dnf copr enable packit/sosreport-sos-4463
• And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.

[TurboTurtle]

Plugin.get_dir_listing() exists for standardized directory listing collections. Please use that for these.

[abetkike]

Thank you for the review feedback @TurboTurtle . I've revised the code to use Plugin.add_dir_listing() for the rsyslog directory collections (note: I used add_dir_listing() as that's the available method - I assume that's what you meant by get_dir_listing()).

Current implementation (revised):
self.add_dir_listing(['/var/', '/var/lib/', '/var/lib/rsyslog/'],
extra_opts='d')
self.add_dir_listing('/var/lib/rsyslog/')

My question:

The first call uses add_dir_listing() with extra_opts='d' to show the directory hierarchy with SELinux labels. This generates three separate output files (one per path):

• ls_-alZd_.var
• ls_-alZd_.var.lib
• ls_-alZd_.var.lib.rsyslog

The original command (ls -ldZ /var/ /var/lib/ /var/lib/rsyslog/) captured this hierarchy in a single file, which made it easier to see the SELinux context progression along the path.

Would you prefer:

1. Current approach: Both commands use add_dir_listing()
2. Mixed approach: Keep hierarchy as add_cmd_output("ls -ldZ /var/ /var/lib/ /var/lib/rsyslog/") (single file), and use add_dir_listing() only for the directory contents

Thanks for your guidance!

[arif-ali]

in my opinion, we should use add_dir_listing() for both