Playstation 3 and the Linksys WRT54G Wireless-G Boardband Router

November 24, 2007
James Skemp

While I initially hooked up my Playstation 3 a week ago, when I was posting to the official PS forums today, my second post, I was doing so to recommend a version of the router I'm using. Since both items are pretty popular now, it makes sense to write up a quick guide on them, I suppose. My equipment First off, there's my setup. I've had pretty experiences with Linksys, but poor experiences with Netgear, so Linksys I am.

November 6, 2007
James Skemp

In a previous article, I gave an overview of the World Wide Web Consortium (W3C) extended log format, in relation to Internet Information Services (IIS) 6.0. This time, I'd like to cover what each field provides, again in relation to IIS and a Web site, for statistical and debugging purposes. What fields are available Again, we've covered what fields are available in the W3C extended log format in a previous article.

November 3, 2007
James Skemp

In Microsoft Internet Information Services (IIS) 6.0, you can choose to use a number of different formats for your access logs. Access logs contain information about what files are requested, whether the request was successful or not. Of all the available formats, the World Wide Web Consortium (W3C) extended log file format is by far the most flexible format available, as you can select the information that you would like to log.

October 25, 2007
James Skemp

The following is a high-level look at Log Parser's (version 2.2) SQL syntax. This does assume that you understand the specifics of each part, but for those that do not, this will be covered in a future tutorial. (This is more for my use.) Bolded elements are required for any valid query, whereas the other elements are optional. SELECT USING INTO FROM WHERE GROUP BY HAVING ORDER BY Again, details about the specific parts, with real-world examples, will be covered in a future tutorial.

October 6, 2007
James Skemp

In IIS 6.0, you can setup Application Pools for each of your sites. My knowledge of the exact benefits of this is somewhat lacking, but what I do understand is that these help applications (Web sites) stay within their own bounds, and prevent them from having a bad effect upon each other. For example, if one application is preforming poorly, as long as it's not a server-wide issue, the other sites on the server will be impacted minimally.

October 1, 2007
James Skemp

Note: This article was written using Log Parser 2.2. Therefore, while it may work for a different version, it may not. The following SQL can be used by Log Parser to generate a chart with the total requests (for a day, month, or year) and what percent each status code is of those requests. An example chart can be found at the end of this article. First, I assume that the below is put in the same directory as the logs you would like to parse.

September 19, 2007
James Skemp

A few days ago my server was restarted in the early morning hours. I had been logging network and processor usage using Windows built-in performance monitoring, but when the server restarted, the logs did not. A bit of research later, it appears that there is a way to have Windows restart the logging after a system restart. To enable this, it seems you just need to have the log stop after a certain amount of time (for example, after x hours, or x days).

September 13, 2007
James Skemp

The following Log Parser query can be used on FTP log files in order to determine what user names were used to login, or attempt to login, to an FTP site. logparser "select cs-uri-stem, count(cs-method) from ex*.log where cs-method like '%USER' group by cs-uri-stem order by count(cs-method),cs-uri-stem" This assumes that you've added Log Parser to your path, and that you're running this from your log file directory. This query will tell you what ip addresses successfully logged into your FTP site.

September 9, 2007
James Skemp

Note: This article was written using Log Parser 2.2. Therefore, while it may work for a different version, it may not. In a previous article, I discussed how to use Log Parser to find 404 errors in IIS log files. This time, I've made it a little broader, by giving some queries to find all 400 codes, and all 500 codes, through log files. There may be a better way to find these codes (instead of my IN statement), but a standard LIKE doesn't seem to work.

September 5, 2007
James Skemp

The follow covers how to compile BlogEngine.NET from the most recently available source code. This was originally posted to the Codeplex discussions for BlogEngine.NET, and will eventually get moved into the wiki. (Update Sept 8, 2007: Added to the BlogEngine.NET wiki, but not yet linked from other pages. Also made a minor change to step one.) Compiling source with Microsoft Visual C# 2005 Express Edition 1) Download the current source code from the Releases tab or the Source code tab on CodePlex.

Newer

Older

Search

Links of Note

Support This Site

If my blog was helpful to you, then please consider visiting my Amazon Wishlist.

Playstation 3 and the Linksys WRT54G Wireless-G Boardband Router

W3C extended log format fields and IIS 6.0

A brief overview of IIS 6.0 and the W3C extended log format

Log Parser SQL query syntax (high-level)

Determining which IIS 6.0 Application Pool belongs to which application

Log Parser script: Percent of status codes across all hits/requests

How to ensure that performance counters continue after a restart

Using Log Parser to find users accounts used to log into an FTP site

Log Parser queries to find 400 and 500 http status codes

Compiling BlogEngine.NET source with Microsoft Visual C# 2005 Express Edition

Search

Links of Note

Recent Posts

categories

Support This Site