Say why macOS fsck Logs keeps its Source File column - #316
Merged
Merged
Conversation
On the MacBook Pro logical extraction the Program column tells the two logs apart (fsck_apfs.log and fsck_hfs.log), but it cannot separate every file the artifact reads: /var/log/fsck_hfs.log and each user's Library/Logs/fsck_hfs.log all hold fsck_hfs runs. The notes now say so. Notes only; no output changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Notes only. Says why macOS fsck Logs keeps its Source File column: Program separates the two logs on the tested MacBook Pro, but /var/log/fsck_hfs.log and each user's Library/Logs/fsck_hfs.log all hold fsck_hfs runs, so Program cannot tell every file apart.
🤖 Generated with Claude Code