Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 02 Nov 2018 23:25:40 +0000
From:      "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To:        "Mark Johnston" <markj@freebsd.org>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: [CFT] capsicum patches for rtsol(8) and rtsold(8)
Message-ID:  <F249C24A-4637-43DE-A14A-08C0376B7666@lists.zabbadoz.net>
In-Reply-To: <20181024195627.GI45118@raichu>
References:  <20181015194212.GA2751@spy> <E9282C14-3AEE-4D07-BD0A-38550F974DA9@lists.zabbadoz.net> <20181016165308.GB5066@raichu> <86D87437-BD34-489A-87B7-33F1089080EE@lists.zabbadoz.net> <20181016200414.GD5066@raichu> <2A564C8A-FB64-4D2A-9E3E-392F1FCA66BD@lists.zabbadoz.net> <20181024195627.GI45118@raichu>

next in thread | previous in thread | raw e-mail | index | archive | help
On 24 Oct 2018, at 19:56, Mark Johnston wrote:

Hi,

sorry I lost track on this.

> Yes, I just uploaded a new version of the patch to
> https://people.freebsd.org/~markj/patches/rtsold_capsicum.diff and =

> would
> appreciate any further testing that you can do.

The rtsol Makefile does not cleanly apply to my HEAD.

Also there seems to be an empty .else case in both rtsold and rtsol =

Makefiles.

Also I couldn=E2=80=99t get rtsol to link until I realised that it was re=
scue =

which didn=E2=80=99t want to link (-j24 output can be confusing).  I gues=
s =

with -DSMALL gone and MK_CASPER not turned off for rescue or whatever it =

is the result is not what we expect?

Just a few lines for you.

=2E.
   15229                                                                 =

     ^
   15230 1 warning generated.
   15231 iscsid_stub.c:1:70: warning: implicit declaration of function =

'main' is invalid in C99 [-Wimplicit-function-declaration]
   15232 int _crunched_iscsid_stub(int argc, char **argv, char =

**envp){return main(argc,argv,envp);}
   15233                                                                 =

      ^
   15234 1 warning generated.
   15235 =

/tank/users/bz/obj/tank/users/bz/git_bz_experimental_v6only/amd64.amd64/t=
mp/usr/bin/ld: =

error: undefined symbol: cap_init
   15236 >>> referenced by _$$hide$$ rtsol.lo rtsock.c
   15237 >>>               rtsol.lo:(_$$hide$$ rtsol.lo main)
   15238
   15239 =

/tank/users/bz/obj/tank/users/bz/git_bz_experimental_v6only/amd64.amd64/t=
mp/usr/bin/ld: =

error: undefined symbol: cap_service_open
   15240 >>> referenced by _$$hide$$ rtsol.lo rtsock.c
   15241 >>>               rtsol.lo:(_$$hide$$ rtsol.lo main)
   15242
   15243 =

/tank/users/bz/obj/tank/users/bz/git_bz_experimental_v6only/amd64.amd64/t=
mp/usr/bin/ld: =

error: undefined symbol: cap_service_open
   15244 >>> referenced by _$$hide$$ rtsol.lo rtsock.c
   15245 >>>               rtsol.lo:(_$$hide$$ rtsol.lo main)
   15246
   15247 =

/tank/users/bz/obj/tank/users/bz/git_bz_experimental_v6only/amd64.amd64/t=
mp/usr/bin/ld: =

error: undefined symbol: cap_service_open
   15248 >>> referenced by _$$hide$$ rtsol.lo rtsock.c
   15249 >>>               rtsol.lo:(_$$hide$$ rtsol.lo main)
   15250
   15251 =

/tank/users/bz/obj/tank/users/bz/git_bz_experimental_v6only/amd64.amd64/t=
mp/usr/bin/ld: =

error: undefined symbol: nvlist_create
   15252 >>> referenced by _$$hide$$ rtsol.lo rtsock.c
   15253 >>>               rtsol.lo:(_$$hide$$ rtsol.lo main)
   15254
=2E.


>>> resolvconf -a will only update /etc/resolv.conf if the info in
>>> /var/run/resolvconf/interfaces/vtnet0 has changed, I believe.  Try
>>> deleting that file too, and then try running rtsol.
>>
>> When I deleted /etc/resolv.conf and then rtsol manually it had
>> re-appeared.  Unclear to me what was in /var/run; I just wanted to =

>> point
>> out the difference in behaviour;  maybe you are right;  I=E2=80=99ll g=
o and
>> check if deleting in /var/run/ as well makes a difference.
>
> I don't observe that behaviour with either the stock or patched
> rtsol(8): for resolvconf(8) to update /etc/resolv.conf (or re-generate
> it), something under /var/run/resolvconf/interfaces needs to have
> changed.  So, in my case, deleting /etc/resolv.conf *and*
> /var/run/resolvconf/interfaces/re0:slaac will cause resolv.conf to be
> regenerated once rtsold(8) decides to re-run resolvconf(8), but
> deleting resolv.conf on its own will not.

I wonder if that=E2=80=99s a bug (unrelated to yours).  I also noticed th=
at =

when my nameservers changed /etc/resolv.conf did not always reflect =

this.

/bz



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F249C24A-4637-43DE-A14A-08C0376B7666>