On my test vault server (OES2 - Linux), eDir will not start anymore. It
was working fine yesterday, but today - no luck. I manually start ndsd
and get errors that eDir isn't listening on TCP or TLS Ports. I take a
look at the ndsd.log file and get a Java HotSpot error report file of
hs_err_pid####.log file.

Looking at that log file, it looks like one of my eDir2eDir drivers
isn't starting and that it is stopping edir from loading.

> #
> # An unexpected error has been detected by HotSpot Virtual Machine:
> #
> # SIGSEGV (0xb) at pc=0x95d48461, pid=30933, tid=2514611104
> #
> # Java VM: Java HotSpot(TM) Server VM (1.5.0_12-b04 mixed mode)
> # Problematic frame:
> # C [libnpkit.so+0x24461]
> #
>
> --------------- T H R E A D ---------------
>
> Current thread (0x0d557180): JavaThread "\VAULT_TREE\pdco\services\servers\IDVault DriverSet\Vault Auth eDir Driver" [_thread_in_native, id=31086]
>
> siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x00000012
>
> Registers:
> EAX=0x00000002, EBX=0x95d8da84, ECX=0x95d92484, EDX=0x00000000
> ESP=0x95e1d15c, EBP=0x95e1d1e4, ESI=0x95e1da14, EDI=0x00000000
> EIP=0x95d48461, CR2=0x00000012, EFLAGS=0x00210202
>
> Top of Stack: (sp=0x95e1d15c)
> 0x95e1d15c: 000000e6 95d826ec 00000000 0d73ee3f
> 0x95e1d16c: 0d73ee3f b7f0b7e0 00000048 95d8da84
> 0x95e1d17c: 00000000 95d915a4 95e1d1e4 95d6d23c
> 0x95e1d18c: 95d915a4 000012a1 0d7bf000 b7c5cc35
> 0x95e1d19c: b7f0b2b0 00000000 00000000 00000002
> 0x95e1d1ac: 00000000 0d9e54d0 00000000 00000000
> 0x95e1d1bc: 00000000 00000000 0d9e54b0 759a12ad
> 0x95e1d1cc: 0d7bf000 00000001 0d7bf298 0d7bf700
>
> Instructions: (pc=0x95d48461)
> 0x95d48451: 00 00 00 00 e9 98 02 00 00 83 45 ec 01 8b 45 c4
> 0x95d48461: c7 40 10 00 00 00 00 c7 04 24 0c 00 00 00 e8 c4
>
> Stack: [0x95d9e000,0x95e1f000), sp=0x95e1d15c, free space=508k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
> C [libnpkit.so+0x24461]
> C [libnpkit.so+0x17c8d] NPKIT_VerifyCertChain+0xfd
> C [libntls.so.2+0x97aba]
>
> Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
> j com.novell.nds.ntls.NTLSSocket.SSL_connect(J)V+0
> j com.novell.nds.ntls.NTLSSocket.connect(Ljava/net/SocketAddress;I)V+106
> j java.net.Socket.connect(Ljava/net/SocketAddressV+3
> j com.novell.nds.ntls.NTLSSocket.<init>(Ljava/net/SocketAddress;Ljava/net/SocketAddress;Ljava/util/PropertiesV+29
> j com.novell.nds.ntls.NTLSSocket.<init>(Ljava/lang/String;ILjava/net/InetAddress;ILjava/util/PropertiesV+30
> j com.novell.nds.dirxml.driver.ssl.ntls.NTLSKmoFacto ry.createSocket(Ljava/lang/String;ILjava/net/InetAddress;I)Ljava/net/Socket;+13
> j com.novell.nds.dirxml.driver.nds.SubscriptionShimI mpl.connect()V+452
> j com.novell.nds.dirxml.driver.nds.SubscriptionShimI mpl.execute(Lcom/novell/nds/dirxml/driver/XmlDocument;Lcom/novell/nds/dirxml/driver/XmlQueryProcessorLcom/novell/nds/dirxml/driver/XmlDocument;+40
> j com.novell.nds.dirxml.driver.nds.DriverShimImpl.ge tSchema(Lcom/novell/nds/dirxml/driver/XmlDocumentLcom/novell/nds/dirxml/driver/XmlDocument;+253
> "hs_err_pid30933.log" 630L, 44303C


Is there anyway to set this driver to a manual start instead of auto in
a file somewhere so I can see if eDir will startup then.

Thanks,
Mike