Actually it looks like the issues I'm seeing on OS X have nothing at all to do with the endianness. Content-length seems to be incorrect here for some reason. Investigating now. If anyone else is trying to run pushpool on OS X, please drop me a note. Would love to compare notes / sanity check.

Update: the problem had to do with strndup on OS X. Fixed and pushed to my fork at http://github.com/zapnap/pushpool. If someone else is using OS X I'd love to hear from you .

I patched pushpool awhile back so it would compile on OS X but I still seem to have some issues getting clients to talk to it. Is anyone else having any level of success on OS X or *BSD platforms with the endian fixes?

Of course . Just seemed strange not to apply a base level of security to the worker passwords as well (particularly since so many users re-use passwords).

So I patched pushpool to compile on OS X, which jgarzik was kind enough to pull into the master branch. However, I'm still having an issue with it that hopefully someone can help me with.

It seems that pushpool initializes, and binds to a port (as defined in the config) but then immediately dies on me. Has anyone experienced similar problems? Ratcheting the logging up to the max level and using -E to redirect stderr reveals no additional information.

Also, a database schema question... it appears that the intent is that the password column should be plaintext. Is there an explicit design reason for this? Wouldn't it be far better to encrypt the values stored there and run a database PASSWORD() function to check the match?

Cheers,

..nap

I'm trying to get pushpool and some other infrastructure-related components squared away for a project I'm working on. It'd be immensely helpful if I could interact with folks on the appropriate boards... I've actively contributed patches via github, etc. Thanks for the consideration...

Edit by Maged:
Could you provide some more information? Perhaps you could link one of the patches you've done on Github?