Re: Can't specify different names for config file in project data

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============6500427981606512615==
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="1zvXuOXJBGUn8mUIaxnCOBJlaSJHOdEDA"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--1zvXuOXJBGUn8mUIaxnCOBJlaSJHOdEDA
Content-Type: multipart/mixed; boundary="dIKd5961NIgVBYdue6DC3fzP4VnfBCR9n";
 protected-headers="v1"
From: Christian Grothoff <[email protected]>
To: [email protected]
Message-ID: <[email protected]>
Subject: Re: [bug-GNUnet] Can't specify different names for config file in
 project data
References: <[email protected]>
In-Reply-To: <[email protected]>

--dIKd5961NIgVBYdue6DC3fzP4VnfBCR9n
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

This shouldn't be the case, as GNUnet picks up the (default) service
contact information from a the share/gnunet/config.d/ directory.

Also, when I change the value, everything still works for me. What is
the error message you are seeing (if any)?

On 9/1/19 11:51 AM, Alessio Vanni wrote:
> The GNUNET_OS_ProjectData struct contains two fields, `config_file' and=

> `user_config_file'.  By default they are set to "gnunet.conf" and
> "~/.config/gnunet.conf".
>=20
> When these fields are set to a different name, the application refuses
> to start.  It seems the problem is caused by the fact that the
> application is unable to find the required informations to connect with=

> GNUnet, i.e. the specified file must be a copy of gnunet.conf instead o=
f
> containing only the application-specific configuration for the
> application to work.
>=20
> A.V.
>=20
> _______________________________________________
> Bug-GNUnet mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/bug-gnunet
>=20


--dIKd5961NIgVBYdue6DC3fzP4VnfBCR9n--

--1zvXuOXJBGUn8mUIaxnCOBJlaSJHOdEDA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE2EI7yzJseQcDOSnHk55r4eKfw8wFAl1wVEEACgkQk55r4eKf
w8yDshAAhj1DtmAGh6h2JzcWz5Vp4P5uBn0sHUEsoEdOu+/a5btBnPjhTS1jj3as
9vSgNG7NhYduTAVvENHxFb0N0Bm2wNjl7X5X8Qh12JVla2qljEMGeIJT55aR5nT4
86z3XW+B9dNNrOMGP2zvU+NWPKsy+gxQVti5UIvmGDy5U7W1fAvRbpoCV4CYzy5S
Kgu747lehtqP6YCizHGWYteER8Y2EYjtnfH94aTwAPdG1ySq+Mcm/Qqe61ysPJDI
4ltgnS05xwNRji50hubWUxJxyaeCEtq2KsQ225kuUY9oxYyUrsKkWO78ngEs3Tbk
rZHvkB9N0cUHfvD4pw9Ocp/cG3uQnFxs6YFk1Fns3tet9pKvXWTlHzmvjbwrP7aJ
Z0CpgxPi4s2fJDvMFz8lNrGcynFrgOgZws75aQHh5zwQo78VtjlJJ3D8a9btMsk2
qD0ZLOqycLaYdTN4gyYjdvEH2J+fuWYx/iIL9D5bsjSyHLJRQPYeEdSx5rNOz8/3
jN2/bH6+7Z002uWSBgSAfb/lsvcJ5I+hzQIQKDkjJHxtadhYTEKwGAwWAFEfRfJ+
Vkc1aiSLKS264+A4dhq6Udd7ZHBD4EPuUF51tfpk4U0LpnqObkrommPT4mHTU88l
QdkmmZxOfAHGdu0L7eZGD3K3TXVLpkLsQWq85m0W5tVHkeqoHGg=
=fxkU
-----END PGP SIGNATURE-----

--1zvXuOXJBGUn8mUIaxnCOBJlaSJHOdEDA--


--===============6500427981606512615==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KQnVnLUdOVW5l
dCBtYWlsaW5nIGxpc3QKQnVnLUdOVW5ldEBnbnUub3JnCmh0dHBzOi8vbGlzdHMuZ251Lm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2J1Zy1nbnVuZXQK

--===============6500427981606512615==--