It seems upon captive portal startup the captiveportal.db file is not written out until the /etc/rc.prunecaptiveportal script is run.   If the Operator decides to visit status -> captive portal right after enabling the service they will be greated with some nasty nasty errors.  Silence this nonsense by creating a blank captiveportal.db file right after nuking it.
It seems upon captive portal startup the captiveportal.db file is not written out until the /etc/rc.prunecaptiveportal script is run.   If the Operator decides to visit status -> captive portal right after enabling the service they will be greated with some nasty nasty errors.  Silence this nonsense by creating a blank captiveportal.db file right after nuking it.

phil-davis/pfsense,dennypage/pfsense,NOYB/pfsense,dennypage/pfsense,ch1c4um/pfsense,ch1c4um/pfsense,NewEraCracker/pfsense,brunostein/pfsense,jxmx/pfsense,dennypage/pfsense,pfsense/pfsense,ch1c4um/pfsense,ch1c4um/pfsense,NewEraCracker/pfsense,dennypage/pfsense,jxmx/pfsense,brunostein/pfsense,ptorsten/pfsense,ptorsten/pfsense,jxmx/pfsense,BlackstarGroup/pfsense,NewEraCracker/pfsense,phil-davis/pfsense,BlackstarGroup/pfsense,pfsense/pfsense,pfsense/pfsense,BlackstarGroup/pfsense,NOYB/pfsense,ptorsten/pfsense,phil-davis/pfsense,pfsense/pfsense,BlackstarGroup/pfsense,phil-davis/pfsense,NewEraCracker/pfsense,NOYB/pfsense,brunostein/pfsense