Ah, I should have been more clear - I was asking if it was, because sometimes that sort of error can be caused be SELinux blocking the bind operation. If it's not enabled, it obviously isn't the culprit though.
Though since you mention OpenVZ... maybe there's something weird with the OpenVZ kernel? Isn't that one of those virtualization methods that has funky kernels that are built just for that kind of virtualization ? Those can sometimes interfere with unexpected things... we have a dedicated server somewhere that is dedicated but still running in some kind of container, and we can't add swap storage, even using a file, due to the kernel ...
On Wed, Jan 15, 2014 at 1:10 PM, Jan Tomasek <jan@xxxxxxxxxx> wrote:
On 01/15/2014 06:57 PM, Jonathan Vaughn wrote:
> SELinux enabled?
No. I would like to avoid that. The server should run inside OpenVZ
container where is not possible to enable it.
--
-----------------------
Jan Tomasek aka Semik
http://www.tomasek.cz/
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
