pfSense » pfSense Packages

Virtually no information here. If you have issues with current pfSense version and current tinydns package version, then post to the forum until you have some identifiable confirmed bug.

https://forum.pfsense.org/index.php?board=15.0

https://github.com/pfsense/pfsense-packages/blob/master/config/tinydns/tinydns.inc#L77

Forum reference for tracking:

https://forum.pfsense.org/index.php?topic=96927.0
https://forum.pfsense.org/index.php?topic=93282.0

I started working through the issues, beginning at tinydns.sh
Unfortunately it was taking more time than I have available, but at first glance it appears that the rewrite to support PBI has a bunch of missing and/or inconsistent paths/references/symlinks.
Further, I noticed differences in presence/absence of files/folders/symlinks depending on whether the system was upgraded from older pfSense, clean install, tinyDNS reinstall (over the top), or tinyDNS reinstall (remove and then install).
I suspect somebody ran a search'n'replace on the scripts and did no more than a single clean install on a fresh system for testing.
Sorry I don't have more details, and it'll be at least couple months before I can circle back to this, hopefully this is enough to help somebody else dig into it further. :(

(This is an issue in 2.2.3 as well as 2.2.1)

@Michael: These issues won't go away until the PBI shit dies in 2.3. Meanwhile, I looked at the code and the only fix I can offer is symlinking a bunch of stuff to /usr/loca/bin. If that's not acceptable, I'm not touching this. Way too much pain to rewrite the heredocs in the XML file to work around PBI's idiotic paths.

Err... not XML, but tinydns.inc; the point obviously stands, though. (I suspect that beyond /usr/local/bin/svscan, also /usr/local/bin/svc does not exist normally, plus possibly others.)

https://github.com/pfsense/pfsense-packages/pull/909

Die, PBI, die!!! #$%^@!!! :-X

Confirmed working by multiple forum users, safe to close. ;)