SDS

so far so good... we are only putting out 50% of the data we put out last Sunday, but we essentially have zero load right now, so that bodes very well for us.

Isobars???? Damn, you have been going to college!

yeah, but they had something to play for in recent weeks. Now, the team could be packing it in, but Kitna could come up big.

I think the guy wants to show how he has been wronged.... this game means something to him.

an image I could have done w/o!

If BG offered me that cash, I'd root for his sister getting hit by a bus! j/k

I'll be disappointed if this rig takes a plunge at 5:00 pm.

Did you bump into Chuck in the laundry room scrubbing jocks?

Figure for 2005

I tried there. also in /home/mydir Grrrrrr.... this stuff pisses me off!

I've tried a few locations, but restarting mysql didn't grab the new settings. Where does this go on FreeBSD?

every now and then it is easy to forget we are all on the same side and want the same things - a place to chat with other fans and a SB victory. I'm crossing my fingers that a lot of technical good came out of this and that our maximum capacity is set at a much higher level. I still have a few items to implement/fix, but I'm encouraged so far. So I extend my apologies to anyone who was slighted earlier in the week. I hope everyone has a nice weekend and we'll see you here on Sunday!

that's where I went every week....

well, what gould possibly be solution to a thread that has 895 responses? Show the entire outline every time you read a single message? That is why threaded views are unworkable past a certain volume of posts. Our old board never really had more than 50 replies to a subject. So, you are wishing for a solution from the past that really never behaved as you want it now.

"Boston Fans: You are now free to gloat around the country."

Sorry, but the growth of the board means the old threaded views cannot return - you can't thread 1000 responses in a reasonable fashion. Have you tried viewing the board in outline mode? That is on the top right. That is close as we will ever get to threaded views.

I changed a setting that messed everything up so bad that I couldn't undo it because the board wouldn't reload... My fault! Thanks to the little woman back on the homefront taking unix dictation from me over the phone to fix this.

try it again. if it still doesn't work I need the following: OS version: Browser: gif or jpg: dimension of file: size of file: error message or problem:

as I have changed our setup. This may only affect Safari users.

ok, I know why you don't see it. It's a permissions thing.... I thought I squashed that bug last night. Just hold tight until tonight when I have time to figure out why it worked for me and not you.

tell us more about the avatar you are trying to upload.

1. Most of the perfomance gains were through some piece of code I installed Monday night. 2. Obviously, an empty dB is going to load faster than a full one. That I always knew, but I considered that a band-aid and not a fix - many boards perform great w/o clearing their dBs. Reviews of the largest IPB boards out there revealed that they didn't need to perform this measure. New archiving features installed in the more recent releases of the board make this easier to perform than in the past. I knew it would help in the 2 queries that are made to the forum index page (that used to take 0.1 secs each), but I decided to go ahead and take every reasonable performance gain I can get. I assume this is a 10% type performance gain and not a 400% gain like I am hoping to achieve. Tonight we will be down for a short while as I am installing a fresh copy of the board. The upgrade process over the past 5 versions have left errors that I am now seeing. When that is done, I will finish implementing a new way to handle images that should really take a huge load off the server once it is implemented.

not anymore.... those puppies are cached. and as long as this was some freak thing that rarely happens - it is good news cause it probably explains the load jump at 3:00pm and after. after I killed it - the load went to nothing and the execution time plummeted. My hopes are once again on the rise.

I killed it. It was taking up to 90% of the cpu. this is bad if apache doesn't kill it off. something must be wrong....

what the hell is that top process and why has it been there so long? How do I determine what it is and if it is bad - how do I kill it? last pid: 55970; load averages: 1.46, 1.44, 1.40 up 12+07:54:09 18:35:17 139 processes: 2 running, 137 sleeping CPU states: 30.2% user, 0.0% nice, 69.8% system, 0.0% interrupt, 0.0% idle Mem: 307M Active, 668M Inact, 264M Wired, 776K Cache, 199M Buf, 761M Free Swap: 1020M Total, 23M Used, 996M Free, 2% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 22744 www 61 0 58920K 12364K RUN 127:49 77.83% 77.83% httpd 25992 mysql 2 0 152M 86736K poll 154:25 7.42% 7.42% mysqld 22820 www 2 0 59076K 11648K accept 0:31 0.88% 0.88% httpd 22755 www 2 0 59192K 13120K accept 0:34 0.78% 0.78% httpd 22801 www 2 0 59064K 12516K accept 0:30 0.78% 0.78% httpd 22778 www 2 0 59068K 11528K accept 0:29 0.73% 0.73% httpd 22812 www 2 0 59136K 11592K accept 0:34 0.59% 0.59% httpd 22757 www 2 0 59116K 13176K accept 0:33 0.59% 0.59% httpd 22752 www 2 0 59096K 13276K accept 0:30 0.59% 0.59% httpd 22760 www 2 0 59104K 12568K accept 0:29 0.44% 0.44% httpd 22797 www 2 0 59072K 14372K accept 0:33 0.29% 0.29% httpd 22763 www 2 0 59072K 11808K accept 0:31 0.20% 0.20% httpd