Are you sure it's a path length issue? We usually have a mechanism to
truncate for this.
gnunet-namestore is NOT expected to create the .sock file. This should
exist already if you started the peer properly. Note that the namestore
service is a per-user service, so you if you are using the multi-u
When executing gnunet-namestore for an A or record, the Unix path gnunet-service-namestore.sock is not created. This is because the warning indicates the path is too long. Moreover, there are other system items in that directory.util-client-2744
