> The first time an NSS program loads, it will attempt to load nssckbi -
> the root certificate module , and then store its location into the
> secmod database. If you migrated your profile from EMX to VACPP, this
> would happen. Just delete the secmod.db and everything will be OK - a
> new secmod.db will be created automatically with a pointer to correct
> version of nssckbi found in your LIBPATH.
 
But I use both the VACPP and EMX version with the same profile!

Jens



Reply via email to