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-user setup, you are likely are missing the per-user launch of gnunet-arm (that is, if your peer is running at all). See https://docs.gnunet.org/handbook/gnunet.html#Minimal-configuration On 6/21/20 6:49 PM, William Dobbs wrote: > When executing gnunet-namestore for an A or AAAA record, the Unix path > gnunet-service-namestore.sock <http://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
0x939E6BE1E29FC3CC.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
