I actually ran in to
this same issue for a little while yesterday morning using Suse 9.3 Professional
and PHP4 (installed through Yast). Turns out that somewhere along the line
(either through a Yast update or my own best efforts to break my system), that
some of the PHP4 packages were at different version levels. Once I made
sure that all of my PHP4 packages were the same version and restarted the
appropriate services, JFFNMS came back up just fine. This solution may not
apply to every system, but it could be something to look at
anyway.
<snip>Gu0d M0rrow wrote:
preg_match: internal pcre_fullinfo() > > error -3 in /opt/jffnms/conf/config.parse.func.inc.php on line 19
Mike Concannon
smime.p7s
Description: S/MIME cryptographic signature
