![]() *I've always thought it was bad form to use special chars in paths and files, even though MacOS and HFS/APFS allow it.About fifty feet in that direction, she said, pointing. I'm down a classic rabbit hole, I set out to understand a crash, and hours later, I'm still trying to understand how this stupid path got mis-parsed by the logger. Such a usage makes no sense in the context of a log entry that is reporting an explicit known location.īut HFS is a bit weird, in that it is exceptionally permissive of special chars in paths, provided the char is escaped or the path quoted when used from the shell or system calls. In normal use, a UNIX OS would take that to mean "expand/enumerate all directories under 'Tools/' which contain a subpath like 'SuperDuper!.app/Contents/MacOS/SuperDuper!' ". So, while I'm still trying to understand the crash, this question is whether such a path element has any purpose. Searching the net for stuff like 'MacOS application path asterisk' was fruitless, a few hits reminding us that '*' is a legal char in HFS paths, but you'll need to quote or escape it from the shell. DS_Storeĭrwxr-xr-x 4 taryn admin 128 Application 4 taryn admin 128 ReadMe.rtfd/ĭrwxr-xr-x 3 taryn staff 96 Jun 26 15:16 1 taryn admin 5670 !.plist Palantir_ethernet:Tools taryn$ ls -AlF SuperDuper Ls: SuperDuper/SuperDuper: No such file or directory Palantir_ethernet:Tools taryn$ ls -AlF SuperDuper/SuperDuper Palantir_ethernet:Tools taryn$ ls -AlF SuperDuper/SuperDuper\!.appĭrwxr-xr-x 10 taryn staff 320 Jun 24 22:48 Contents/ rw-r-r- 1 taryn staff 8 Jun 24 22:47 PkgInfoĭrwxr-xr-x 53 taryn staff 1696 Jun 24 22:48 Resources/ĭrwxr-xr-x 3 taryn staff 96 Jun 24 22:48 _CodeSignature/ Nor did drilling through the App's folders offer any insight: Palantir_ethernet:Tools taryn$ ls -AlF SuperDuper/SuperDuper\!.app/Contentsĭrwxr-xr-x 24 taryn staff 768 Jun 24 22:48 Frameworks/ĭrwxr-xr-x 5 taryn staff 160 Jun 24 22:48 Helpers/ rwxr-xr-x 1 taryn staff 94736 Jun 24 22:48 SDDiskTool* Tical bar (`|') after each that is a FIFO.īut that doesn't wash, the asterisk lands in a different spot: Palantir_ethernet:Tools taryn$ ls -AlF SuperDuper/SuperDuper\!.app/Contents/MacOS/ Sign after each symbolic link, an equals sign (`=') afterĮach socket, a percent sign (`%') after each whiteout, and a ver. F Display a slash (`/') immediately after each pathname that is aĭirectory, an asterisk (`*') after each that is executable, an at I'd thought momentarily it was an instance of the -F arg of ls. (note the by the permissions tells us that there are extended attributes on those files.) The asterisk doesn't appear in the finder, nor in shell listings: Palantir_ethernet:Tools taryn$ pwdĭrwxr-xr-x 3 taryn staff 96 SourceTree.app/ĭrwxr-xr-x 7 taryn admin 224 Jun 26 15:16 3 taryn staff 96 The Hit List.app/ĭrwxr-xr-x 3 taryn admin 96 3 taryn admin 96 TinkerTool.app/ Path: /Applications/Utilities/Console.app/Contents/MacOS/Console Path: /System/Library/Frameworks/amework/Versions/A/XPCServices/.xpc/Contents/MacOS/ Path: /Volumes/VOLUME/Applications/Tools/Arduino1.8.9.app/Contents/MacOS/Arduino I first checked other hang files to see if that was simply an artifact of the logger, but none show a similar behavior: Command: Arduino Putting aside the weirdness of an exclamation point in a path*, the asterisk at Tools/*/Superduper!.app has me completely perplexed. Path: /Applications/Tools/*/SuperDuper!.app/Contents/MacOS/SuperDuper! hang file:įrom /Library/Logs/DiagnosticReports/SuperDuper!_-154852_taryn-Palantir-2904.hang. While chasing down why SuperDuper! consistently hangs when quitting after doing a backup, I noticed a peculiar line in this. Under what circumstances does macOS use this? The surprising part is the *, which I've never seen before. SuperDuper! crashed recently, and when looking at the report I found /Applications/Tools/*/SuperDuper!.app/Contents/MacOS/SuperDuper!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |