Fix bug to allow for multiple PIDs to be returned

Bug:
```
[root@pronghorn04 ~]# service salt-minion restart
Stopping salt-minion daemon:                               [  OK  ]
Starting salt-minion daemon: /etc/init.d/salt-minion: line 67: [: 22610:
unary operator expected
                                                           [  OK  ]
```

Traced bug:
```
++ pidof -c -o 21702 -o 21341 -o %PPID -x salt-minion
+ '[' 22610 7606 ']'
/etc/init.d/salt-minion: line 67: [: 22610: unary operator expected
```
master: more narrow scope for unmask

Previously umask could be left as 191 (0277) in some cases.

Though it still needs try/finally, but that's probably another problem
that should be fixed globally via context manager for all umask
changes, e.g.::

    with salt.utils.umask(191):
        do(stuff)
master: fixed direct user query via getpwnam

Previously founduser was set but unused.
remove space around delimiter
remove space around delimiter
Merge branch 'develop' of github.com:saltstack/salt into develop
re patter fix
states.postgres_user manages user attributes

postgres_user.present will make sure that user attributes and password
are the same as what is passed as arguments.
Also, modules.postgres.user_list can return password hashes.
Fixed pylint and unit test errors
Allow the ZMQ to deliver or drop the message before GC. Fixes #9103.
Log to trace instead of print, @pwaller per #9752
Merge pull request #9766 from nateucar/develop

Fix bug #9740 to allow for multiple PIDs to be returned
Merge pull request #9771 from SaveTheRbtz/minor-bugfixes

Minor bugfixes
Merge pull request #9775 from CSSCorp/develop

Re pattern fix and option/value delimiter fix
Merge pull request #9776 from pakdel/postgres_user.present

states.postgres_user manages user attributes
Merge pull request #9780 from s0undt3ch/issues/9103-zmq-assert

Allow the ZMQ to deliver or drop the message before GC. Fixes #9103.
The RabbitMQ add user command requires a password, currently, we can pass
None (as in nil/null) in here, and the rabbitmq module will cast to the string "None".

Here, we ensure that when we're going to clear the password immediatly after creating
the account, we generate a random password. This ensures we don't have an account with
"None" as the password should salt or rabbitmq fail between creating the user, and
clearing the password.
Jail yumpkg behind a config option

The yum api is just too unstable for us to use this as the default
but we will keep it around jailed behind a minion config options
called yumpkg_provider
Merge pull request #9763 from kiall/bugfix/rabbitmq-user-password

Ensure RabbitMQ state never leaves a user with a password of "None"
Shuffling data.extra stuff around