substack/bouncy — Issue #13: Bouncy CLI Fails to Start with Monit
Author: joemccann
Created: 2011-12-01 19:18:43+00:00
State: open

I have a simple monit script that monitors bouncy and works fine, but *only* when I make the following change to the bouncy cli script:

```
#!/usr/local/bin/node
```

if you `npm install -g bouncy` the top looks like this:

```
#!/usr/bin/env node
```

When it is set to the `env` version, monit fails to restart the process which is an init.d script. When it is the direct path to node ( `#!/usr/local/bin/node` ) it restarts it just fine.

There is nothing in the monit script nor the init.d script that is funky. The only delta for when it fails is when I use the `#!/usr/bin/env node` version.

I've checked permissions and all that jazz and everything seems fine. Also, my path is the following:

```
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
```

Any ideas?
```