`znc -d znc-conf` doesn't work.
`znc -d ./znc-conf` works.
`znc -d ~/znc-conf` works.
How to reproduce: just put some perl module to znc-conf/modules/ and try to load it
Possible fix: call realpath() on ZNC startup to make the path absolute
##
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/338999-modperl-fails-to-load-modules-from-znc-dir-modules-when-using-d-option-to-znc-with-relative-path?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:14488032 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
znc -d znc-confdoesn't work.znc -d ./znc-confworks.znc -d ~/znc-confworks.How to reproduce: just put some perl module to znc-conf/modules/ and try to load it
Possible fix: call realpath() on ZNC startup to make the path absolute
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/338999-modperl-fails-to-load-modules-from-znc-dir-modules-when-using-d-option-to-znc-with-relative-path?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).