Skip to content

Say why macOS fsck Logs keeps its Source File column #316

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
abrignoni merged 1 commit into from
Sep 27, 2026
Merged

Say why macOS fsck Logs keeps its Source File column #316

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions scripts/artifacts/macosFsckLogs.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,8 +36,10 @@
"and, when not run as root, writes Library/Logs/fsck_hfs.log in the user's home folder "
"instead "
"(https://github.com/apple-oss-distributions/hfs/blob/d1bac2f062e6e9c0dfcce302d9aacb10173d0eea/fsck_hfs/utilities.c#L358-L369). "
"No tested image held a copy under Library/Logs. Apple's ctime manual gives the local "
"date and time with no offset "
"No tested image held a copy under Library/Logs. Program told the MacBook Pro's two logs "
"apart, but it does not separate every file a row can come from, since "
"/var/log/fsck_hfs.log and each user's Library/Logs/fsck_hfs.log all hold fsck_hfs runs, "
"so Source File stays. Apple's ctime manual gives the local date and time with no offset "
"(https://github.com/apple-oss-distributions/Libc/blob/4e34d0559e3a1b081afeb8604d9e204a1f31321d/stdtime/FreeBSD/ctime.3#L135-L143), "
"so Started (as written) and Completed (as written) are text as stored. A GitHub code "
"search of apple-oss-distributions found no source that writes the fsck_apfs lines; on "
Expand Down
Loading