| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
to their own git repositories
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1751566 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
tools and extras
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1740289 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
| |
As bash isn't specified by POSIX its location is variable.
Specifically under BSDs it isn't found in /bin/bash.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1541763 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
| |
this makes it much easier not to call the python testing code
when it isn't available
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1541241 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
that gets used by clients) in order to avoid port collisions
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1492778 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
sasl_set_path() does no check on the given directory, so when you get bad behavior
later it can be hard to track down. Especially bad is its policy of defaulting to
an alternate standard location if yours fails. That's a potential security bug.
So this patch checks that your dir exists, and is readable, before calling
sasl_set_path(). Either you get the sasl config dir you were expecting,
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1183121 13f79535-47bb-0310-9956-ffa450edef68
|
