-
Anything ‘published’ on the web is viewed as intellectual property and, regardless of whether it displays a copyright symbol or not, is therefore copyrighted by the originator. The only exception to this is if there is a “free and unrestricted reuse” statement associated with the work.
In order to protect our members and TFL from possible litigation, all members must abide by the following new rules:
1. Copying and pasting entire articles from another site to TFL is strictly prohibited. The same applies to articles from print or other media, and to posting photographs taken of copyrighted pages or other media.
2. Copyright law provides for “fair use” of portions of a copyrighted work. You can copy no more than a SINGLE paragraph from the article to your post (3 or 4 sentences at most).
3. You must provide a link to the article along with the name of website. For example: ww.xxx.yyy/zzz (The Lower Thumbsuck Daily News).
4. You must provide, in your own words, a brief summary of the article AND your reasons for believing it will be of interest to TFL members. Failure to do so may result in the thread being closed or your post being deleted as a “cut and paste drive by.”
5. Photographs and other images are also copyrighted. "Hotlinking" of images (so that it appears in your message) from other sites is also prohibited unless you own rights to the image. If you wish to share an image, provide a clickable link to it.
Posts that do not follow these new guidelines will be altered or deleted by staff. Members who continue to violate this policy may lose their posting privileges at TFL.
Thank you for your cooperation and your participation in TFL, the leading online forum for firearms enthusiasts.
What happed to TFL?
- Thread starter ahenry
- Start date
Rich Lucibella
Staff
Unknown.
At 4 AM Monday, I was doing some file maintenance. Noted that the database backup directory was at 97% occupancy due to one large backup file...the most recent.....so I blew it away.
As I hit the Return button, I did a "DOH!". Then I checked the automated tasks...at 4 AM, the system is building the backup...that's why it was temporarily so large.
CRASH!
(Actually, the system should not have crashed...the data files were still in tact. The problem was server load due to the server trying to read/write to non-existent files....but it hung anyway.)
Tried a remote reboot, which would have resolved it and that's when problem 2 reared it's ugly head:
The system does not want to boot up reliably. It continues to hang up at different points in the boot sequence and requires that we have someone physically standing by at the location. Roger went out there at 5:30PM EST yestereday. Between us, we got the system up and I did a repair of the database (nothing lost).
I then ran out and came back at 10:30PM to find the server load maxed out. Tried some ginger manipulations, but ginger wasn't co-operating. Result...I could FTP in, but not get on thru the Web. SWAT was working fine, though...on the same box! As I'd been out to dinner and had a couple of drinks, I left it as I found it....I learned a long time ago that alcohol doesn't mix with server maintenance.
This AM, GlockTalk's Eric called to ask if I needed help. I got him into the server and we started looking around. Finally restarted the Apache server and all looks in order.
Now Known:
We need more memory. 1.25GB ain't making it. I'll start looking to up it to 2GB.
Now Suspected:
There does appear to be a network conflict, probably outside our box at the Web Host center. Eric's suspicion: they never changed the pointers from the temp page that was up during the crash and the network is trippin' and skippin'. Will be working on this also.
Rich
At 4 AM Monday, I was doing some file maintenance. Noted that the database backup directory was at 97% occupancy due to one large backup file...the most recent.....so I blew it away.
As I hit the Return button, I did a "DOH!". Then I checked the automated tasks...at 4 AM, the system is building the backup...that's why it was temporarily so large.
CRASH!
(Actually, the system should not have crashed...the data files were still in tact. The problem was server load due to the server trying to read/write to non-existent files....but it hung anyway.)
Tried a remote reboot, which would have resolved it and that's when problem 2 reared it's ugly head:
The system does not want to boot up reliably. It continues to hang up at different points in the boot sequence and requires that we have someone physically standing by at the location. Roger went out there at 5:30PM EST yestereday. Between us, we got the system up and I did a repair of the database (nothing lost).
I then ran out and came back at 10:30PM to find the server load maxed out. Tried some ginger manipulations, but ginger wasn't co-operating. Result...I could FTP in, but not get on thru the Web. SWAT was working fine, though...on the same box! As I'd been out to dinner and had a couple of drinks, I left it as I found it....I learned a long time ago that alcohol doesn't mix with server maintenance.
This AM, GlockTalk's Eric called to ask if I needed help. I got him into the server and we started looking around. Finally restarted the Apache server and all looks in order.
Now Known:
We need more memory. 1.25GB ain't making it. I'll start looking to up it to 2GB.
Now Suspected:
There does appear to be a network conflict, probably outside our box at the Web Host center. Eric's suspicion: they never changed the pointers from the temp page that was up during the crash and the network is trippin' and skippin'. Will be working on this also.
Rich
Thanks for the hard work in keeping TFL up and running. I appreciate it.Mike Irwin
Staff
I thought I had gotten work blocked, too. Luckily not.