[illumos-Developer] SchilliX-0.7.1 based on b147+ available

Joerg Schilling Joerg.Schilling at fokus.fraunhofer.de
Sun Sep 5 04:49:23 PDT 2010


Gary Mills <mills at cc.umanitoba.ca> wrote:

> > The error message is:
> > 
> > [ Sep  1 23:42:50 Executing start method ("/usr/sbin/ipsecalgs -s"). ]
> > ipsecalgs: Unable to open policy socket: Protocol not supported
> > [ Sep  1 23:42:51 Method "start" exited with status 1. ]
> > 
> > this makes me believe that it could be related to rpc but disabling rpc/bind
> > did not show the problem again...
>
> I'm betting on svc:/system/device/local:default because that service
> runs
>
>     /sbin/soconfig -d /etc/sock2path.d >/dev/null 2>&1
>
> from the devices-local method.  According to the soconfig man page,
> which is out of date on illumos, it does this
>
>      The  soconfig  utility  configures  the  transport  provider
>      driver  for  use  with sockets. It specifies how the family,
>      type, and protocol parameters in  the  socket(3SOCKET)  call
>      are  mapped  to  the  name  of  a transport provider such as
>      /dev/tcp.
>
> My boot chronology shows that svc:/system/device/local:default runs
> about eleven seconds after svc:/network/ipsec/ipsecalgs:default runs
> and fails.

Yesterday, I had a single case with an Illumos based SchilliX where 
svc:/network/ipsec/ipsecalgs:default did run and in this case, this 
was after svc:/milestone/devices:default

It may be better to let it depend on svc:/milestone/devices:default.
What do you think?

Jörg

-- 
 EMail:joerg at schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js at cs.tu-berlin.de                (uni)  
       joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily



More information about the Developer mailing list