Stopping notification server

[hugoduraes]

vagrant halt is not stopping the notification server.

Using Vagrant 1.6.3 on Mac OS X 10.9.3.

[fgrehm]

That sucks :( I don't own a mac so I'm not sure how to reproduce and fix it.

I'm actually willing to extract the tcp server code out to a separate project since I'm willing to use it on a separate project. I'll keep this open until I'm able to take care of that.

[wearhere]

Hm, I can't reproduce @hugoduraes (OS X 10.9.3, Vagrant 1.4.3, vagrant-notify 0.4.0)--I see vagrant-notify-server appear on vagrant up but then disappear on vagrant halt.

However, I do see that vagrant suspend does not kill the server--that might be a nice change.

[hugoduraes]

@wearhere can you upgrade Vagrant to the latest version and test again?

[russjaguar]

I was having this issue on OS X 10.10.1, with Vagrant 1.6.5. I just updated to the latest version of Vagrant (1.7.2 at this time) and I can confirm that when suspending, the notify server is left running and will build up and eventually start blocking Vagrant actions until all the running notify servers are killed. The notify servers are ended properly when using the halt action.

[callistino]

Can I run the tcp server without vagrant?

[fgrehm]

@callistino these days I'd recommend using https://github.com/fgrehm/notify-send-http#vagrant. I'm still thinking about using that as the foundation of this plugin but haven't made my mind yet... @Driklyn has reported that he has been using it with great success and I'd say you give it a try too.

The more people giving me a 👍 on that, the more I'm inclined to think about this plugin a bit more ;)

[alpha01]

Bug fixed on v0.5.0