Timeline for What went wrong with my launchd plist?
Current License: CC BY-SA 4.0
5 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 12, 2023 at 23:04 | vote | accept | hbquikcomjamesl | ||
May 12, 2023 at 16:38 | comment | added | Gordon Davisson |
It doesn't identify it as a shell script, but as a script of some kind -- could be shell, perl (#!/usr/bin/perl ), awk (#!/usr/bin/awk -f ), expect (#!/usr/bin/expect ), etc. Some things (like bash) will assume it's a shell script, but they'll generally do the same thing if it doesn't have a shebang at all.
|
|
May 12, 2023 at 15:32 | comment | added | hbquikcomjamesl | Point taken. Although I'd always understood that it identifies the file as a shell script, albeit without, as you point out, saying anything about what shell to use. And launchd wouldn't already be in a shell, so . . . . | |
May 12, 2023 at 5:33 | comment | added | Gordon Davisson |
A "generic shebang" is not valid. Some things (like bash) may ignore it, but it's not something you should ever actually use. The purpose of a shebang line is to specify the interpreter to use on the file, and #! does not do that.
|
|
May 11, 2023 at 23:45 | history | answered | hbquikcomjamesl | CC BY-SA 4.0 |