with 1.8.x-git-109-4d82211 it doesnt seem possible to save the config when ~.znc is a symlink.
starting the znc works though
with 1.8.x-git-109-4d82211 it doesnt seem possible to save the config when ~.znc is a symlink.
starting the znc works though
<!-- github-sync-id:340408367 -->
i cant tell you how i created it, since i've been using this setup for a long time and both ways creating testlinks look exactly the same in my fs.
the behavior seems to have changed 'lately', since it worked with ~2 month older znc-git.
i cant tell you how i created it, since i've been using this setup for a long time and both ways creating testlinks look exactly the same in my fs.
the behavior seems to have changed 'lately', since it worked with ~2 month older znc-git.
<!-- github-comment-id:404316384 -->
ZNC versioning doesn't matter if the symlink itself is invalid. ~.znc is not the same as ~/.znc, so you need to determine if the symlink is valid or not, first
ZNC versioning doesn't matter if the symlink itself is invalid. ~.znc is not the same as ~/.znc, so you need to determine if the symlink is valid or not, first
<!-- github-comment-id:404318738 -->
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.
with 1.8.x-git-109-4d82211 it doesnt seem possible to save the config when ~.znc is a symlink.
starting the znc works though
Did you try symlinking ~.znc or ~/.znc?
i cant tell you how i created it, since i've been using this setup for a long time and both ways creating testlinks look exactly the same in my fs.
the behavior seems to have changed 'lately', since it worked with ~2 month older znc-git.
ZNC versioning doesn't matter if the symlink itself is invalid. ~.znc is not the same as ~/.znc, so you need to determine if the symlink is valid or not, first
Sorry for wasting your time.
the symlinked partition was full :/