Okay now this is making more sense. I have had the backup cache go
nuts on me as well so there is defiantly a bug lurking somewhere in
there.
Scott
On 2/13/07, Angelo Turetta <[EMAIL PROTECTED]> wrote:
Sean Cavanaugh wrote:
> upgrade that thing to one of the new snapshots and try and see if i
Sean Cavanaugh wrote:
upgrade that thing to one of the new snapshots and try and see if it
happens still. snapshots seem more stable than even the 1.0.1 release.
Of course will do.
Though the problem discussed here was not my panic (which I'm pretty
sure recent relases/snapshots has solved), bu
upgrade that thing to one of the new snapshots and try and see if it happens
still. snapshots seem more stable than even the 1.0.1 release.
-Sean Cavanaugh
> Date: Tue, 13 Feb 2007 13:25:20 +0100> From: [EMAIL PROTECTED]> To:
> support@pfsense.com> Subject: Re: [pfSense Su
Scott Ullrich wrote:
I cannot reproduce this one. I would say something in your XML is
nice and hosed. If you ever accidentally updated to -HEAD then this
is surely part of it.
Scott
On 2/10/07, William Armstrong <[EMAIL PROTECTED]> wrote:
Warning: Invalid argument supplied for foreach() in
I cannot reproduce this one. I would say something in your XML is
nice and hosed. If you ever accidentally updated to -HEAD then this
is surely part of it.
Scott
On 2/10/07, William Armstrong <[EMAIL PROTECTED]> wrote:
Warning: Invalid argument supplied for foreach() in
/etc/inc/xmlparse.inc
Warning: Invalid argument supplied for foreach() in
/etc/inc/xmlparse.inc on line 184 Warning: Cannot modify header
information - headers already sent by (output started at
/etc/inc/xmlparse.inc:184) in /usr/local/www/diag_backup.php on line
102 Warning: Cannot modify header information - headers
