- Posted on
Fri Sep 16, 2016 8:12 am
-
Different Computers
offline
-
- Posts: 2544
- Joined: Jan 02, 2016
- Location: East Coast
-
man, I must have been drinking when I tried to make this run at startup.
the launchctl plist still had USERNAME for the user name.
Fixed that.
Still doesn't seem to start up the shell script when I make launchctl load it.. But when I start the shell script manually, now I get
- Code: Select all
[9/16/2016, 10:06:22 AM] Homebridge is running on port 51826.
[9/16/2016, 10:07:54 AM] Got SIGINT, shutting down Homebridge...
So it looks like two problems:
1. launchctl still isn't finding the script
2. the script runs, but something sends a SIGINT and shuts the process down as soon as it finishes starting up.
I'll pound on the first problem, but I have no idea how to troubleshoot the latter. And keep in mind, again, HomeBridge runs just fine when I start it in a terminal window!
So for problem 1, should this line in the launchctl plist
- Code: Select all
<string>/Users/USERNAME/runhomebridge</string>
actually be
- Code: Select all
<string>/Users/USERNAME/runhomebridge.sh</string>
?
Because it seems like it's referring to the shell script by file name, and its name is runhomebridge.sh.
SmartThings refugee, so happy to be on Indigo. Monterey on a base M1 Mini w/Harmony Hub, Hue, DomoPad, Dynamic URL, Device Extensions, HomeKitLink, Grafana, Plex, uniFAP, Fantastic Weather, Nanoleaf, LED Simple Effects, Bond Home, Camect.