On Wed, Nov 06, 2019 at 04:29:16PM +0100, Otto Moerbeek wrote:
> On Wed, Nov 06, 2019 at 04:16:10PM +0100, Felix Maschek wrote:
>
> > Hi,
> >
> > unwind is running and does talk to 9.9.9.9 (checked with DNS Leak Test -
> > bash.ws <https://bash.ws/dnsleak>):
> >
> > vatrox$ ps -A | grep unwind
> > 42668 ?? Ip 0:00.01 /sbin/unwind
> > 42070 ?? IpU 0:03.27 unwind: resolver (unwind)
> > 43163 ?? Ip 0:00.09 unwind: frontend (unwind)
> > 59857 ?? Ip 0:00.01 unwind: captive portal (unwind)
> > 72389 p1 R+/2 0:00.00 grep unwind
> >
> > The socket is missing:
> >
> > vatrox$ ls /var/run
> > ConsoleKit cron.sock dev.db ld.so.hints rc.d
> > syslog.pid utmp
> > apmdev dbus dmesg.boot ntpd.sock smtpd.sock user
>
> Strange. Tge code is structured in such a way that failure to cerate the
> socket is fatal.
>
> Once thing to try:
>
> run
> ktrace -i rcctl start unwind
>
> and then
> rcctl stop unwind
> kdump > /tmp/d
>
> amd inspect /tmp/d to find out what happended to the socket.
Hmm that does not work.
stop unwind and do:
ktrace -i /sbin/unwind
ktrace -C
kdump > /tmp/d
Search for unwind.sock in /tmp/d
-Otto
