rabbitmq-run.mk: Fix stop-brokers with NODES > 1

[jeckersb]

Remove extra "1" in seq command. Previously, as an example with
NODES=2, will run seq 2 1 which produces no items to iterate, so the
entire stop-node loop does not execute and the brokers are left
running.

(This should qualify as an Obvious Fix for CLA purposes)

[pivotal-issuemaster]

@jeckersb Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

[pivotal-issuemaster]

@jeckersb This Pull Request contains an obvious fix. Signing the Contributor License Agreement is not necessary.

[michaelklishin]

Thank you. We will take a look at this after our team-wide getaway that's happening this week.

[dumbbell]

Hi!

Thank you for the patch. Indeed, the seq(1) command on Linux doesn't produce the expected output which should be "2 1" in this example, to stop the brokers in the reversed order.

Could you please modify your patch so that the command is seq $(NODES) -1 1?

[jeckersb]

@dumbbell thanks, makes much more sense to stop them in reverse order :)

[dumbbell]

Thank you, I merged your patch.

That was my mistake. I only tested this on my workstation running FreeBSD and seq(1) on BSD doesn't have the same default behavior regarding the implicit increment as the GNU implementation. So the usual Works On My Machine™ :-)