Greasing Bearings - How Much is Enough?

Written by Thomas Yoon

Previously, we have talked about using suitable greases for different applications. Basically, we want to use low temperature greases for low temperature applications and high temperature greases for high temperature applications. The reason is quite simple - we wantrepparttar grease to form a thin film of lubricating oil betweenrepparttar 133383 rubbing surfaces.

If we use high temperature grease for normal temperature applications,repparttar 133384 chances arerepparttar 133385 grease will still be in semi-solid state and will not flow to coverrepparttar 133386 contact surfaces ofrepparttar 133387 moving components during operating conditions.

Assuming you have chosenrepparttar 133388 correct grease, how do you determine how much you need to put intorepparttar 133389 bearing?

Excessive grease lubrication can easily cause overheating. The grease gets churned around withinrepparttar 133390 moving parts ofrepparttar 133391 bearing and has nowhere to go. The temperature rises. The grease becomes repparttar 133392 wrong temperature selection even thoughrepparttar 133393 application is correct.

A general rule to follow is thatrepparttar 133394 bearing should be filled completely butrepparttar 133395 free space inrepparttar 133396 housing only partially. This gives room forrepparttar 133397 grease to be ejected fromrepparttar 133398 bearing on start-up.

However, there is some grease,repparttar 133399 so-called "totally-filled" greases like lithium soap greases that can allow filling up to 90% ofrepparttar 133400 free space inrepparttar 133401 housing, without risk of a temperature rise. This is because they are special. Their stability at high temperatures is excellent and can be utilized over a wider temperature range than sodium soap greases.

Which w3wp.exe process belongs to which App Pool in IIS6

Written by Scott Forsyth

Along with Windows Server 2003 and Internet Information Services 6.0 came a large number of benefits. For us IIS admins, it was a great welcome set of changes. But, one apparent difficultly is matching uprepparttar w3wp.exe processes displayed in Task Manager torepparttar 133382 Application Pools in IIS.

Review of IIS5

In IIS5.0 (Windows 2000 Server), each site that is set to Out Of Process will spin up a new instance of dllhost.exe. Windows Task Manager lists them. Now,repparttar 133383 trick is to find out which dllhost.exe matches which site. My favorite way is to use Component Services. To do so, open Component Services from Administrative Tools, drill down to Computers -> My Computer and select COM+ Applications. Now select View fromrepparttar 133384 top menu and select Status. Beside each site that currently has a dllhost.exe process spun up isrepparttar 133385 Process ID (PID). Using Task Manager, you can tellrepparttar 133386 memory and CPU.

Note: Ifrepparttar 133387 Process ID doesn't display for you in Task Manager, select View -> Select Columns and add it.

What about IIS6?

But, that doesn't work anymore with IIS6.0. Now each site in IIS6 is placed in an Application Pool. Each Application Pool is completely separated from other App Pools by running in its own process called w3wp.exe. This make life SO much easier. Now,repparttar 133388 trick is to match uprepparttar 133389 process shown in Task Manager withrepparttar 133390 Application Pool set up in IIS.

If there is a different user for each application pool, Windows Task Manager isrepparttar 133391 easiest way to find out which application pool belongs to which site since Task Manager will displayrepparttar 133392 userrepparttar 133393 process runs as.

Cont'd on page 2 ==> © 2005
Terms of Use