Tim Nelson wrote:
please post your logs somewhere that can be accessed on demand
I have found pastebin to be quite useful for sharing text
http://pastebin.com/
-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For
On Thu, Feb 12, 2009 at 2:05 PM, Atkins, Dwane P atki...@uthscsa.edu wrote:
We upgraded to pfSense version 1.2.2 today around 0530. It seems to have
upgraded just fine and personnel started logging into the CaptivePortal and
I tested it as well and it worked as expected. However, around 11:30
On Thu, Feb 12, 2009 at 2:05 PM, Atkins, Dwane P atki...@uthscsa.edu wrote:
We upgraded to pfSense version 1.2.2 today around 0530. It seems to have
upgraded just fine and personnel started logging into the CaptivePortal and
I tested it as well and it worked as expected. However, around 11:30
While some of us are on an 'unlimited' connection, I'm sure some users in
addition to the mail server do not have this freedom. In the future, please
post your logs somewhere that can be accessed on demand instead of pushing
nearly 1MB of log data to EVERY member of the mailing list. TIA.
Tim
On Thu, Feb 12, 2009 at 2:38 PM, Tim Nelson tnel...@rockbochs.com wrote:
While some of us are on an 'unlimited' connection, I'm sure some users in
addition to the mail server do not have this freedom. In the future, please
post your logs somewhere that can be accessed on demand instead of
Sent: Thursday, February 12, 2009 1:37 PM
To: support@pfsense.com
Subject: Re: [pfSense Support] Issues with upgrade to pfsense version
1.2.2
On Thu, Feb 12, 2009 at 2:05 PM, Atkins, Dwane P atki...@uthscsa.edu
wrote:
We upgraded to pfSense version 1.2.2 today around 0530. It seems to
have
upgraded
On Thu, Feb 12, 2009 at 2:57 PM, Atkins, Dwane P atki...@uthscsa.edu wrote:
The captive portal page was locked up. It appears that there was a php
issue around 11:00 or so.
Scott, where would I find the 1.2.3 release?
http://snapshots.pfsense.org/FreeBSD7/RELENG_1_2/?C=M;O=D
It has been
Don't know if it's changed in the 1.2.2 and 1.2.3 releases, but in 1.2-RELEASE
the CP wasn't very well suited for high-volume concurrent logins. Each client
spawns its own thread that tries to gain an exclusive lock on the flat file
that enumerates sessions, then linearly searches that for a
