Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Feb 2015 14:30:14 -0800
From:      Garrett Cooper <yaneurabeya@gmail.com>
To:        Miguel Clara <miguelmclara@gmail.com>
Cc:        freebsd-current <freebsd-current@freebsd.org>
Subject:   Re: Shared object "libsodium.so.13" not found, required by "dnscrypt-proxy"
Message-ID:  <98CF988A-D9DB-49AD-8CFF-3B438F892730@gmail.com>
In-Reply-To: <CADGo8CUo=QUV904F7PsndiB%2B6pcYBD%2B1gC7tNZkswRvRNWEB4Q@mail.gmail.com>
References:  <CADGo8CURnvyLD55zs5m=hgrG9g6xct0q4ZMSNiY%2BzLA1GBi0Ug@mail.gmail.com> <CAGHfRMC1_jRQxkxu-aaJJBvqb8oPvOrCiJwOWhLsR1A81YKrEw@mail.gmail.com> <CADGo8CWyyFJXR5fD%2BYe%2BSynzH0mqfh3Fsx8ULmQzOxTwR0Bd8A@mail.gmail.com> <FF6DD5BB-7D15-4224-8EF5-DA1C89908B1B@gmail.com> <B506CD41-42F8-4DAF-B2D3-B09C70A2A28D@gmail.com> <64AF7708-217B-4AC0-A47A-AD1B0BFF7EDC@gmail.com> <CADGo8CUCCjrW-3p9F4aiwRh1fbid%2BfNjikag55%2BNheJYBUt-Rg@mail.gmail.com> <885DA4D0-9644-4F06-97C9-04EAD7B4958C@gmail.com> <CADGo8CVjVig6HT6o2MYMzXizFLG62WMEFTe278nq8qoOg3-akQ@mail.gmail.com> <CAN6yY1tKDi4da25KbpATRnOE7YZOgVyw78rBrH4wofF3iqQLXQ@mail.gmail.com> <CADGo8CV4=4V31ibc9S43e3bBC1g3YL-m-NLc2Bccz_Pk4fQ49Q@mail.gmail.com> <CADGo8CV4ziyTxJJstLm9VWFueLGVjkZ=Kt6hhV1owymSMf7=yg@mail.gmail.com> <CADGo8CUeexNbOW8VbjNQ8-UGrsVny5JO4Ckv89XNg9v-aEetSA@mail.gmail.com> <CAN6yY1tpyinY1yueHY8Tr=igQbkTpwJBdz9-aUwQ5xdMqiVf-A@mail.gmail.com> <CADGo8CUo=QUV904F7PsndiB%2B6pcYBD%2B1gC7tNZkswRvRNWEB4Q@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--Apple-Mail=_8EF2C81B-252A-4E59-85EB-19D97258E75E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

On Feb 25, 2015, at 14:19, Miguel Clara <miguelmclara@gmail.com> wrote:

...

> I noticed this too, but in that case why doesn't it affect all users? =
(or all the ones using dnscrypt+local_unbound) maybe something changed =
in "NETWORKING" recently?
>=20
> Hum:
> =
https://svnweb.freebsd.org/base/head/etc/rc.d/NETWORKING?r1=3D275299&r2=3D=
278704
>=20
> Interesting, as I am using the most recent version which does not =
REQUIRE local_unbound=20
>=20
> I'm even more confused now :|
>=20
>=20
> So it has to come after SERVERS but before local_unbound. But =
NETWORKING depends on local_unbound they are both dependent on NEWORKING =
which has to be after SERVERS. Can you say fubar! Clearly broken. And =
this means that removing SERVERS will re-shuffle the order more =
appropriately.=20
>=20
> It seems that the behavior of rcorder is not as documented as well as =
being undefined when circular dependencies occur. The man page says that =
rcorder aborts when it encounters a circular dependency, but that is not =
the case. It probably is best that it not die, but that leaves things in =
an unknown and inconsistant state, which is also a very bad idea. I =
guess when a circular dependency is encountered, a dichotomy occurs.

Now you know why I=92m so curious about all of this stuff.

When I was working on ^/projects/building-blocks, I was able to move =
most of these pieces around by changing REQUIRE: to BEFORE:, but I =
noticed that it changes the rcorder a bit, so I haven=92t been super =
gung ho in implementing my change.

I think there are a couple bugs present on =
9-STABLE/10-STABLE/11-CURRENT:

- Things go awry if named is removed/not installed.
- Things go awry if local_unbound is removed (which would have been the =
case if the rc.d script was removed from your system, which existed =
before my changes).
- Other rc.d scripts not being present might break assumptions.

I need to create dummy providers for certain logical stages (DNS is one =
of them) to solve part of this problem and provide third parties with a =
mechanism that can be depended on (I wish applications were written in a =
more robust manner to fail gracefully and retry instead of failing flat =
on their face, but as I=92ve seen at several jobs, getting developers to =
fail, then retry is hard :(=85).

Another short-term hack:

Install dummy/no-op providers so the ordering is preserved, then remove =
the hacks after all of the bugs have been shaken out.

Thanks!

--Apple-Mail=_8EF2C81B-252A-4E59-85EB-19D97258E75E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJU7kz2AAoJEMZr5QU6S73eeZQH/1JxWeI2gjWjXs8IvcRQXEU9
JHehb2dlThJTe0gkvqyWlauTlZlIvNN3kHC337hqEKp2IxUNL5Byj8k/R8YC/G6w
/L9yDpz0h0f72jOh7iJxFFdUvWIpLofqlIe4HNQfzuOeql+QaENIjraNoQNQeXIh
1U+y4ecoeUVDUoGgBxiSZfWQEPbtV2c+QpCzo6bw9wuU9CzvxXTw+fNEqicaLfaT
yUHTbMgBurCjZ4dXxESO513stwAarS8zHRT8PNd4+PQSJzfAB4RGck/78B7IS7LI
KzNEELp8l3vAQyjtF1TokStoHqmu83J1HKyqJ6pj/+3yyIYQ8hkx7my2GcZtuKc=
=jzyU
-----END PGP SIGNATURE-----

--Apple-Mail=_8EF2C81B-252A-4E59-85EB-19D97258E75E--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?98CF988A-D9DB-49AD-8CFF-3B438F892730>