From cca1ca55b1ee8e38c14e75e606c411711f7157cf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Philippe=20Rivi=C3=A8re?= Date: Thu, 9 Feb 2017 23:36:30 +0100 Subject: [PATCH] explanations for macOS / brew + troubleshooting hints --- examples/init/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/examples/init/README.md b/examples/init/README.md index 9af8c74..37c3a73 100644 --- a/examples/init/README.md +++ b/examples/init/README.md @@ -109,10 +109,12 @@ Similar to `systemd`, on OS X you can run `go-ipfs` via a user LaunchAgent. ``` The reason for running `ipfs` under a shell is to avoid needing to hard-code the user's home directory in the job. +If you installed IPFS with `brew install ipfs`, change the path accordingly to e.g. `/usr/local/bin/ipfs` + - To start the job, run `launchctl load ~/Library/LaunchAgents/io.ipfs.go-ipfs.plist` Notes: -- To check that the job is running, run `launchctl list | grep ipfs`. +- To check that the job is running, run `launchctl list | grep ipfs`. It should give you a line such as this: `1234 0 io.ipfs.go-ipfs`; a dash in lieu of a PID is a sign of failure: check system.log in your Console.app. - IPFS should now start whenever you log in (and exit when you log out). - [LaunchControl](http://www.soma-zone.com/LaunchControl/) is a GUI tool which simplifies management of LaunchAgents.