I just updated to a recent ‑current and tried the new nullfs. Sockets (e.g. the MySQL one) work now with nullfs. No need to have e.g. jails on the same FS and hardlink the socket to not need to use TCP in MySQL (or an IP at all for the jail).
Great work!
[6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44] [45] [46]Share/Save [47]
2 Comments To "Sockets and nullfs: works now in ‑current"
#1 Comment By Remko Lodder On March 18, 2012 @ 14:05
Hi Alexander,
This is great news! This should be in 9 hopefully as well (I am using that) since this is a feature we would love to use! 🙂
Do you know of problems within the FreeBSD Jails and NULLFS + PHP dirname? (it results in empty output)
#2 Comment By netchild On March 18, 2012 @ 16:09
I have Horde-Webmail, Gallery2 and PHPMyAdmin on such a system. I haven’t checked yet more than an initial connection to all of them, but if they use dirname during the initial connection, I haven’t seen an negative effect.