Hi everyone! For now if Log5F can’t to load the log5f.properties config, it turns off, it doesn’t send any messages. But I’m not sure that this is convenient. You can say what you think about this in pool or comments for improve Log5F. Thanks!

This is a vintage postcard of the Buckingham Sawmill and Dufferin Falls in Buckingham, Quebec. In recent times, Buckingham has been amalgamated into Gatineau. Gatineau is located in Quebec’s Outaouais region.

Reverse of Postcard

Some Buckingham surnames at the end of the 19th century

Addy – Allen – Arnaud – Baker – Barkley – Barns – Bastien

Baulne – Beauchamp – Beaudin – Beave – Bedard – Bernard – Bernardin

Bertrand – Bigelow – Bissare – Blais – Boileau – Boisvert – Bouchard – Boucher

Bourassa – Brazeau – Brennan – Brewer – Bugeron – Burgess – Burke

Busby – Butler – Cameron – Campbell – Campeau – Carrier – Cassidy

Cavan – Chamberlin – Chambers – Charbonneau – Charon – Charpentier

Chartrand – Cheney – Chenier – Clement – Cloutier – Constantineau

Cooke – Copeland – Corbeil – Corrigan – Cosgrove – Cote – Coughlin – Cox

Culican – Currie – Dale – Daoust – Davis – Dean – Deault – Degagne – Delorie

Desjardins – Didier – Dionne – Dodge – Donaldson – Dore – Dougherty – Dowd

Doyle – Driscoll – Drouin – Dufresne – Dugal – Dumond – Ethier – Etienne

Farwell – Filiatrault – Fitzgerald – Flemming – Flood – Fournier – Fraser – Freeman

Ganot – Garvey – Gauthier – Gilbert – Gillis – Gleeson – Gollingher – Gorman – Goulette – Gowder

Groton – Grotton – Guartin – Hall – Hamelin – Hayes – Healy – Higginson – Hogan

Jaindin – Joinet – Joyce – Judge – Kelly – Kendall – Kennedy – Lacelle – Lachance

Lafleur – Laframboise – Lahaie – Lahair – Lamoureux – Lanagan – Landry – Lapointe

Larin – Larocque – Larose – Larvee – Lawson – Legare – Limoge – Lonergan – Lonsdale

Lough – Lowe – Lynch – Lyons – Mahony – Marin – Martin – Matte – Maurin

McAndrews – McArthur – McCabe – McCay – McCollum – McConnel – McDermot – McDonald

McDonnell – McFarland – McFarlane – McFee – McG- McGivern – McGuire – McKenzie

McLemens – McMillan – McNamara – McNaughton – McNulty – McPeak – McPike – McShane

McWaters – Menard – Michaud – Miller – Moran – Morisette – Morris – Murphy

Newton – Normand – O’Dowd – O’Driscoll – O’neil – Page – Palmer – Paquette – Paquin

Parker – Pattens – Pearson – Pelletier – Pennal – Plamondon – Power – Pratt – Prince – Proudfoot

Proulx – Renaud – Robb – Robillard – Ross – Rowe – Ryan – Sarrazin – Sharpley – Shopleg

Simeon – Smith – Soucy – Spense – Spooner – St-Amour – St-Ange – Stevenson – Stewart

Stone – Story – Strickland – Tessier – Tetehault (Tetrault/Theriault?) – Thompson – Tremblay – Valier

Vezina – Villeneuve – Wallace – Warwick – Waters – Welsh – Wilson – Windsor

Wiseman – Woods – Woods

Related Posts:

Vintage Postcards of Quebec

The lemur is under threat from a “timber mafia” which is pillaging the island’s forests for profit, conservation groups have warned.

Madagascar, which has been isolated from landmasses for more than 160m years, is the world’s fourth largest island and a “conservation hotspot” with thousands of exotic species found only here. These include nearly 100 species of lemur, six of which are deemed critically endangered.

But decades of logging, mining and farming have destroyed 90 per cent of Madagascar’s forests, though the rate has slowed in the past two decades, the Guardian reports.

The former president, Marc Ravalomanana, was praised for putting 6m hectares under protection and backing eco-friendly community projects and sustainable farming. But Mr Ravalomanana was ousted in March in a violent coup that led to a “gold rush” of armed loggers and poachers.

Now lemurs’ natural habitat is again under threat from the accelerating deforestation.

In addition, the endangered animals are being hunted for bushmeat, either to be eaten by drought-afflicted local populations or sold as a roasted delicacy in city restaurants.

Dr Hantanirina Rasamimanana, a researcher and teacher at Antananarivo University, told the paper: “Deforestation is always a problem, but in these past five months bushmeat is also very dangerous. People are desperate because of the lack of rain.”

She added: “Here in Madagascar, when there is a political change, everything is burning. It’s always like that. They burn, they cut, they destroy, they steal. “If they don’t stop, I am afraid that some species will become extinct.” Conservationists say that armed gangs are exploiting the security vacuum to pillage rosewood and ebony from supposedly protected forests on behalf of a so-called “timber mafia”.

This year an estimated $100m worth of hardwood has been cut down and sold, mostly to China to be turned into furniture.

Source: Telegraph, 18 Nov 2009

In the spirit of Thanksgiving and large-scale turkey consumption, we wish to acknowledge the impact of turkeys on forest history. How did a couple of turkeys change history? Well, a better question might be: How did a handful of angry turkey hunters in West Virginia upend U.S. Forest Service timber management policy and help usher the agency into the environmental era?

Around 1964, a handful of hunters went to their favorite spot on the Monongahela National Forest in West Virginia to hunt turkey. There, they found no turkeys because the area had been clearcut by the Forest Service. Upset, they took their complaints to the agency, eventually getting a meeting with Chief Ed Cliff, and demanded an end to clearcutting as a timber management practice. As Cliff says in an excerpt from his oral history Half A Century in Forest Conservation, “It soon got beyond the turkey hunting issue.” Indeed, what started off as a disappointing hunting trip for some buddies eventually led to Congress rewriting the Forest Service’s Organic Act and forever changing the agency.

Gobble gobble hey! Any chance you guys are going to West Virginia? (FHS image #R9_492831)

After several years of studies and discussion that changed nothing, the hunters turned to the Izaak Walton League and other conservation groups, and together they filed a lawsuit to stop the use of clearcutting as a harvesting method. Ironically, the outrage wasn’t over clearcutting per se, but over the size of the clearcuts. Nonetheless, the plaintiffs asserted that the Forest Service was in violation of the Organic Act of 1897, which allowed the cutting of “dead, matured, or large growth” trees that had been “marked and designated” for sale. Clearcutting removed all trees; no one bothered marking individual trees since they’d all be removed. No matter, said the court. The law is the law. Izaak Walton League v. Earl Butz was found in favor of the hunters and overturned “the whole legal basis for timber management on the national forests.” Congress now had to write a new organic act for the agency. The resulting National Forest Management Act changed how the Forest Service managed the national forests. Things were never the same for the agency after its passage in 1976 — additional protests and lawsuits further shaped and influenced how the agency conducted management. Ultimately, this led to its turn away from emphasizing timber management and to its embrace of ecosystem management.

This gross oversimplification of a major turning point in forest history is explored in numerous articles and books, many of which we’ve published. But we thought we’d pull two nuggets from our U.S. Forest Service History Collection to share with you. The first PDF is a one-page excerpt from Ed Cliff’s oral history. The second is from The Monongahela National Forest, 1915-1990, which weaves together oral histories and secondary sources into a solid history of the forest. This lengthy excerpt delves into the background of clearcutting on national forests and does a great job of providing context for the controversy, as well as showing that the agency was not monolithic in its thinking. So, on Thanksgiving Day, just before you drift into that tryptophan coma after eating too much turkey, think about how different history would be if only some turkeys had been hanging around in that clearcut in West Virginia.

LocalConnectionAppender can be easy configured for using with debug applications which developed for MiniDebugTarget of Flex Logging Framework.

For this You just set parameters connectionName to _mdbtrace and methodName to trace in configuration of this appender.

This is example log5f.properties config:

<configuration xsi:noNamespaceSchemaLocation="log5f.properties.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:log5j="http://log5f.org">
  <root level="ALL" appenders="minidebug"/>
  <appender name="minidebug" class="org.log5f.appenders.LocalConnectionAppender">
    <param name="layout" value="org.log5f.layouts.PatternLayout" type="Class">
      <param name="conversionPattern" value="%d{ABSOLUTE} [%p] %C{0}.%M %m" type="String"/>
    </param>
    <param name="connectionName" value="_mdbtrace" type="String"/>
    <param name="methodName" value="trace" type="String"/>
  </appender>
</configuration>

Now all log messages from application sends to MiniDebug’s based applications, for example this outputs in Flex Console:

Log messages in Flex Console.

]]> http://cleangreensustainable.wordpress.com/2009/11/23/protecting-americas-public-lands-a-national-concern/ Mon, 23 Nov 2009 18:43:26 +0000 Matthew Koehler http://cleangreensustainable.wordpress.com/2009/11/23/protecting-americas-public-lands-a-national-concern/

The following perspective is from Keith Hammer. Mr. Hammer grew up hiking, skiing, camping, hunting, and fishing in the Swan Mountains of Northwest Montana. He has worked a number of jobs, from Forest Service trail worker to logger to backcountry guide, and currently works as an environmental consultant and head of the nonprofit Swan View Coalition, which he co-founded in 1984. Keith and Swan View Coalition have gotten over 600 miles of road decommissioned on the Flathead National Forest to restore fish and wildlife habitat.

Protecting America’s Public Lands a National Concern!
By Keith Hammer, Swan View Coalition

We can take much inspiration from Ken Burns’ film “The National Parks: America’s Best Idea” and readily extend its premise to the remainder of America’s public lands. Key take-home messages in Burns’ film are that threats to America’s wildlands never cease and that their protection is brought about through national concern and legislation, often over the objections of local politicians.

Indeed, as elk and bison were being slaughtered by commercial hunting in the West in the late 1800s, it was not the new states of Montana and Wyoming that put an end to it. It was Representative John Lacey of Iowa who prohibited the interstate transport of illegally killed wildlife when his “Lacey Act” was signed into law by President William McKinley in 1900.

Montana Senator Thomas Long objected to what is now Glacier National Park being designated a Forest Preserve in 1900, followed by the Kalispell Chamber of Commerce objecting to its designation as a National Park in 1910. Thank goodness for the persistence of Americans George Bird Grinnell and others, who had the foresight to see that the area needed better protection than that afforded the Forest Preserves (later known as National Forests) and convinced President Taft to designate Glacier as America’s 10th National Park!

Today, local communities thrive on tourists visiting Glacier National Park and the families and businesses choosing to locate near it! More recently, the town of Seward, Alaska was so dead-set against the designation of Kenai Fjords National Park that it passed two resolutions denouncing the idea. After the Park was designated in 1980 and Seward began to reap the rewards, however, it rescinded its previous resolutions and asked that the Park be expanded! President Carter, once burned in effigy in Alaska for his conservation initiatives there, nonetheless tripled the size of Denali National Park and designated most of it Wilderness for added protection.

For these reasons and more, we helped write and support the Northern Rockies Ecosystem Protection Act knowing it may not initially garner support from Congressional delegations in Montana, Wyoming, Idaho, Washington, and Oregon. It builds upon President Clinton’s – and now Obama’s – intention to protect roadless lands from development, sequestering carbon in roadless forests also serving as wildlife migration corridors. It also creates high-paying jobs restoring watersheds through road reclamation .

In contrast, Senator Tester’s (D-MT) wildlands logging bill (Links: here, here and here) would set dangerous precedent by mandating logging levels on two National Forests and subsidizing the burning of public forests as “biomass.” It would also release from protection numerous roadless lands and Wilderness Study Areas granted protection by the far-sighted Senator Lee Metcalf in 1977!

Because I’m waaaaay interested in logging, tracing, diagnostics, analytics – basically, what’s going on with my shit – I spent some time today tweaking our log4net configuration here at work. The actual motivation for sitting down and doing this was that I wasn’t getting any notification from uncaught exceptions in our sites, and I saw a couple in the event log on our live box. Naturally I flew into a blind rage and immediately set up an SmtpAppender for the existing log4net config for that site. After an hour or so I have a configuration that I like, so here it is.

I added two things:

• Split configuration files so we can drop a new log4net configuration into a site without worrying too much about the main web.config
• SmtpAppender for any log messages at WARN level or above

Here’s the template web.config file with the log4net configSource attribute:

The debug log4net config file:

And the release log4net config file:

I’ll be suggesting that this configuration is adopted as standard for all new builds and I’ll go and reconfigure a few of our other active sites too.

I have heard that 200 acres of land is being cleared in my neighborhood. Someplace back in the woods – way out – I can hear the equipment working and the evidence of destruction passes my house all day long. 18-Wheelers full of wood chips and logging trucks full of freshly cut huge trees pass by from around 4:30 am until whenever they finish for the day.

Big Trucks on Little Roads

There is a tree farm way out a little, one lane road and I assume that is where the trees are coming from.  I can’t even imagine how these monstrous trucks are getting out there.

The thing is, last winter – all winter- the same thing was happening, but the trees were coming from another area. Supposedly these trucks will stop once the snow falls. They won’t be able to get to the area where the cutting is taking place.

So I’ve heard.

I know that people have to make money and that trees are needed for building supplies, etc., but it is still sad to think of a forest being destroyed.
And I really dislike meeting up with these trucks on my small dirt road…as you can see in my photo – it’s not a very wide roadway and I especially dislike the fact that the school bus must also pass them!

I love living in the country, but there is a price to pay.

Logging

I created test application for live testing Log5F’s work – Test Application. Now it uses next appenders:

Trace Appender:

<appender name="trace" class="org.log5f.appenders.TraceAppender">
  <param name="layout" value="org.log5f.layouts.PatternLayout" type="Class">
    <param name="conversionPattern" value="%d{ABSOLUTE} [%5p] %C{0}.%M - %m%n" type="String"/>
  </param>
</appender>

Firebug Appender:

<appender name="firebug" class="org.log5f.appenders.FirebugAppender">
  <param name="layout" value="org.log5f.layouts.PatternLayout" type="Class">
    <param name="conversionPattern" value="%d{ABSOLUTE} %c{1} - %m%n" type="String"/>
  </param>
</appender>

XPanel Appender:

<appender name="xpanel" class="org.log5f.appenders.XPanelAppender">
  <param name="layout" value="org.log5f.layouts.PatternLayout" type="Class">
    <param name="conversionPattern" value="%c{} - %m" type="String"/>
  </param>
</appender>

LocalConnection Appender:

<appender name="minidebug" class="org.log5f.appenders.LocalConnectionAppender">
  <param name="layout" value="org.log5f.layouts.PatternLayout" type="Class">
    <param name="conversionPattern" value="%d{ABSOLUTE} [%p] %C{0}.%M %m" type="String"/>
  </param>
  <param name="connectionName" value="_mdbtrace" type="String"/>
  <param name="methodName" value="trace" type="String"/>
</appender>

This appender uses LocalConnection’s setting such as MiniDebugTarget from Flex Logging Framework therefore it can be used for sending log messages to consoles which uses for working with MiniDebugTarget, for example Flex Console.

and XMLSocket Appender for Chainsaw:

<appender name="chainsaw" class="org.log5f.appenders.XMLSocketAppender">
  <param name="layout" value="org.log5f.layouts.Log4JLayout" type="Class"/>
  <param name="host" value="localhost" type="String"/>
  <param name="port" value="4448" type="Number"/>
</appender>

Every programmer eventually finds a need to display warnings, debug information, or just status updates as they build their code and watch it run.  Lots of times this takes the form of streaming text to std::cout. But, what if you only want certain information to print at certain times, or you’d like to suddenly change from logging to a terminal to logging to a file?

After several tries, I came up with my logger class.  Basically, using static class members and c-style macros, I came up with a logging method that turns on and off easily, allows easy redirection, and is easy to use everywhere in your code.

At it’s simplest, this logger is used as such:

#include <iostream>
#include "logger.h"

using namespace std;	

int main (int argc, char * const argv[]) {
	bool someLogType = true;
	LOG(someLogType) << "This will be logged to clog\n";
	return 0
}

But the logger class also offers globally accessible log types and the ability to redirect the output wherever you want. The following snippet shows this use.

#include <iostream>
#include <sstream>
#include "logger.h"

using namespace std;	

int main (int argc, char * const argv[]) {
	// Set these to turn various logs on or off dynamically
	NORMAL = true;
	DEBUG = false;
	VERBOSE = true;

	LOG(NORMAL) << "This will log\n";
	LOG(DEBUG) << "But this one won't\n";
	LLOG(VERBOSE) << "This one will log, but with the name of the logtype prepended to the message\n";

	// Now we redirect the log output to a custom location.  This could be a file or any ostream
	stringstream newLog;
	logger::setOutstream(newLog);

	LOG(NORMAL) << "This will log\n";
	LOG(DEBUG) << "But this one won't\n";
	LLOG(VERBOSE) << "This one will log, but with the name of the logtype prepended to the message\n";

	string results = newLog.str();
	cout << "In the new log: \n" << results << "\n";

	// Always reset the logger to clog before the program exits or you will get a BAD_ACCESS error
	// I'm still trying to work out that problem, but this is an easy fix for now
	logger::setOutstream(clog);
	return 0;

}

Get the code here:

• logger.h
• logger.cpp
• example.cpp

Good luck and good coding!

Hi,

Every CRM has more or less custom applications. A custom application may be an ASP.NET, integration between different systems or plug-in / workflow assemblies.

For every application that we are implementing in CRM, it is a good practice to implement a logging system.

This logging system will be logging errors, warnings and informational messages.

I’ve built a web service for this logging purposes. The methods are eventually have no return values. I want to send the log message to the web service and then do not want to wait the result. This makes sense from a performance point of view.

For this purpose, i use a special attribute with my web methods. This attribute is “SoapDocumentMethod” attribute. With this attribute i am able to mark the method as a one-way method.

This approach makes my method a “one-way” method. In this case my logging web service automatically returns a 200-OK status code to the client. This really increases performance and a good approach.

Hope this helps.

Clear cut

It’s a delicate subject around here.  Toss a coin up in the air and decide.  Should the land ever be clear-cut?  Should the trees be sliced off like a razor cutting whiskers on a stubbly chin? 

Foresters often say that in certain areas a clear-cut is advisable.  Many tracts are not good hardwood sites; they refuse to grow beautiful hardwoods like maple and yellow birch which have high-quality value.  If  foresters selectively harvest on these sites they never see much improvement.  If they want to have productive tracts, they will sometimes choose to clear-cut.  The result will be thick aspen (poplar) stands.  In 40-50 years these will be big harvestable trees.  The mills need these stands to mix with their hardwood.

There.  I have just given you forestry-speak.

Keep turning around in a circle

I could share the perspective of someone who loves trees; someone who doesn’t much like the labels of which trees are “valuable” and which trees are “junk”.  I could share old Native American stories about the trees being our brothers and sisters, the lungs of the planet earth.

But no.

I want to talk about the clear-cuts of our soul.

When God calls a Time Out

What times in our own lives have we felt like we’ve been clear-cut?  When everything has been torn away?  When things safe and familiar and loving have been ripped asunder?

Have we all had clear-cuts?  Some clear-cuts come on the heels of endings of relationships.  The endings of friendship, of love, of romance, of marriage.  Some come with the tears of loss:  the death of a child, a spouse, a parent, a grandparent, a friend.  Others have lost their home, their money, their job.  A clear-cut is a place in life where our beloved past meets destructive saws.  The dear trees fall.  So often don’t we weep?  We weep from the loss, the pain, the absence of the loved one.

Stump and dried flower

Afterward the brush lies all over the ground of ourselves.  We wipe our tears and stand straight.  We have to walk with faith, then, through the clear-cut of the soul.  The seeds are growing beneath the tangled brush, but we don’t know it yet.

In a few days or months or years the new trees will be growing.  We will persevere. 

The horizon

I have known many forests who have been heavily logged.  In my lifetime, I have not intimately known many forest tracts completely clear-cut.  Yes, we see clear-cuts everywhere.  But they usually aren’t on land that I have walked, loved, whispered to, dreamed upon.

Once, a long time ago, while crying in some beloved logged forest, an inner thought arose,  “Just sit here until you can feel the sacred beauty of the place.”  I sat for a long time surrounded by impenetrable brush and jagged logs and wild disarray.  I sat with the memory of the tall hemlock, the sturdy maple, the feel of the forest.  I was not going to move until it felt sacred once again, until the invisible seeds of hope and new life showed themselves.

And finally, I saw it.  A flower.  Blossoming.  And over there a precious sweep of branches.  And over there a bent cedar. 

Slowly the logged forest started revealing its promise.

We will grow again, the trees said.  We won’t be the same trees.  But we will grow again. 

Hope

I think of a dear friend who lost her husband three or four years ago.  The first year of her clear-cut was agonizing.  She wondered if she would survive.  I wondered if she would survive.  The second year was filled with many tears, but slowly the young sprouts grew.  She still grieves, but she’s stronger now.  Her new roots are growing into the earth.  It wasn’t something she wanted, but  she’s learned to see the sacred beauty in what remains.

Blessings for all of us in times of the clear-cuts of our soul.

I wrote a while back about how I managed to add logging with log4net to my ProjectWhite tests in Visual Studio. However, after being forced to move my source code it suddenly didn’t work anymore eventhough I followed my amazing instructions. After trying a whole bunch of things out, one of them worked.

For log4net to work, the log4net.config file needs to be copied into the TestResult folder created by Visual Studios testrunner. In order to achieve this, enter the “Test” menu in VS, select “Edit Test Run Configurations”, “Deployment” and there, add your log4net.config file.

This made things work for me.

Note: I’m using the built-in testrunner in Visual Studio to drive my tests and not NUnit right now.
Note2: The first thing I did was setting it up as I did in my previous post, I haven’t tried to see if just adding the file to deployment is enough, it might not be.

How do I log only INFO statments on console and all DEBUG statements in log file? This was a question infront of me.
If you know log4j a bit you might expect it to be very simple to do (even I thought the same). You could do this very easily by using two different loggers
for INFO and DEBUG statements which is kind of annoying. I wanted to have any class-level logger to log its INFO and DEBUG seperately. Below is what I want to achieve.

public class LoggerTest {
	public static void main(String args[]){
		Logger log = Logger.getLogger(LoggerTest.class);
		log.info("I should go to console");
		log.debug("I should go to a log file");
	}
}

Finally, I came to a solution which worked very well for me.
log4j.properties has some limitations like, you cannot specify filters in it. Hence I used log4j.xml.

  <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd" >
<log4j:configuration>
	<appender name="debugfile"
		class="org.apache.log4j.RollingFileAppender">
		<param name="maxFileSize" value="500KB" />
		<param name="maxBackupIndex" value="5" />
		<param name="File" value="debug.log" />
		<layout class="org.apache.log4j.PatternLayout">
			<param name="ConversionPattern"
				value="%d{HH:mm:ss} %5p %5M.%C - %m%n" />
		</layout>
		<filter class="org.apache.log4j.varia.LevelRangeFilter">
			<param name="LevelMin" value="debug" />
			<param name="LevelMax" value="debug" />
		</filter>
	</appender>

	<appender name="stdout" class="org.apache.log4j.ConsoleAppender">
		<layout class="org.apache.log4j.PatternLayout">
			<param name="ConversionPattern"
				value="%d{HH:mm:ss} %5p %5M.%C - %m%n" />
		</layout>
	<!-- Apply filter to output only INFO logs in the console -->
		<filter class="org.apache.log4j.varia.LevelRangeFilter">
			<param name="LevelMin" value="info" />
			<param name="LevelMax" value="info" />
		</filter>
	</appender>
<!--Configured "com.abc" to log only DEBUG statements to the log file
	It will ignore all other statements since we have set the level to DEBUG (least priority)
	-->
	<logger name="com.abc" >
		<level value="debug" />
		<appender-ref ref="debugfile" />
	</logger>
<!--Configured Root to log only INFO statements into STDOUT since we want
	 only INFO statements to be displayed in the console.
	-->
	<root>
		<level value="info" />
		<appender-ref ref="stdout" />
	</root>
</log4j:configuration>

Configure a logger of your root of the package hierarchy to log in a debug file. For example, if your package hierarchy starts with say com.abc then configure a logger named “com.abc” to log in a debug file.
This will make every class-level logger inside com.abc pkg to log its debug statements in a debug file. Okay at this point we are done with the first requirement.

Now, lets look how to log info statements to console. For this, we dont have to create another logger. We can utilize RootLogger which is the parent of all loggers in log4j.
Since we have configured “com.abc” to log only debug statements it will ignore the info statements. Those statements are the bubbled up the hierarchy and respected by the RootLogger which we have
configured to log INFOs to the console. Mission accomplished

This just in:

Senator Tester and his mandated logging bill have “racked” up a major and important endorsement from the fine folks at “Outdoor Life,” who have named Senator Tester part of “The Outdoor Life 25.”

These are the same “Outdoor Life” folks that bring you:

“Rack Girls 2009“

“Fish N Chix 2010“

“Shed Hunting Babes“

Yep, those “Outdoor Life” folks are all about big rack collaboration. Clearly their support of Senator Tester’s logging bill means something…but what that is isn’t exactly clear.

Just read the entire “Outdoor Life” entry about Senator Tester and his logging bill and it’s very clear that “Outdoor Life” has a better handle on big racks hoisted in the air by bikini-clad women than they do on public lands and wilderness policy.

From Outdoor Life:

“For more than 25 years, some 600,000 acres of Montana backcountry have been lost in bureaucratic limbo, legal leftovers from pitched battles between wilderness zealots and timber barons. Described on maps as “wilderness study areas,” these alpine peaks, timbered slopes and foothills grasslands have been off-limits to logging and mining, but have also been a sort of no-man’s land for hunters, anglers and landscape preservationists [Totally not true as every single Wilderness Study Area is currently open to hunting and fishing. - MK]

Are “study areas” open to resource development, or are they locked up in wilderness? Every Montana politician for a generation has tried to untangle the land-use stalemate before being cowed by one interest group or another. Now, thanks to a U.S. senator with a flat-top haircut and a butcher’s build, hunters will be able to access these lands, watersheds will be preserved and unemployed loggers and mill workers will go back to work. Jon Tester crafted his landmark “Forest Jobs and Recreation Act” to preserve the majority of land as wilderness, but require sustainable timber harvest on much of the rest.

There’s something for everyone, but not enough for a single group to claim victory. The collaborative agreement is being eyed by conservationists across the nation as a model for resolving similarly intractable issues.” [Not true...but it sure sounds nice!  Fact is "conservationists across the nation" are pretty much in agreement about their opposition to Senator Tester's Mandated Logging Bill and the sloppy, bad-precedent-setting Wilderness language contained in the bill. - MK]

Here’s a handy way to handle uncaught exceptions in ASP.Net MVC 1.

Make a base controller with the following code:

Then make your other controllers derive from this one and hey presto, friendly(er) error messages and better exception logging in your site.

Sources:

http://geekswithblogs.net/SanjayU/archive/2009/11/09/error-handling-in-asp.net-mvc-1-part-2-of-2.aspx

http://stackoverflow.com/questions/362514/asp-net-mvc-current-action

Error Number 0xc800020e: An incremental backup cannot be performed when circular logging is enabled.

Solution: Disable Circular Logging  

To disable circular logging:*

1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.

2. If the Administrative Groups branch exists in the left pane, expand it, expand the appropriate administrative group’s branch, expand the Servers branch, and then expand the appropriate server’s branch. If the Administrative Groups branch does not exist, expand the Servers branch in the left pane, and then expand the appropriate server’s branch. To expand a branch, double-click the branch or click the plus sign (+) to the left of the branch.

3. Right-click the storage group you want, and then click Properties.

4. To disable circular logging, click to clear the Enable circular logging check box, and then click OK.

5. Restart the information store. To do so:

a. Click Start, point to Programs, point to Administrative Tools, and then click Services.

b. Click Microsoft Exchange Information Store in the right pane, and then on the Action menu, click Restart. If a dialog box appears stating that additional services will be restarted, click Yes.

NOTE: The information store must be restarted because when it starts, it reads configuration information from Microsoft Windows 2000 Active Directory. The Active Directory attribute associated with the circular logging setting is called MSExchESEParamCircularLog. When circular logging is enabled, this attribute is set to 1. When circular logging is disabled, it is set to 0.

Additional Information:

Description of Circular Logging* 

In the standard transaction logging used by Exchange 2000 Server, each database transaction in a storage group is written to a log file and then to the database. When a log file reaches a certain size, it is renamed and a new log file is created. Over time, this results in a set of a log files. If there is a crash, you can recover the transactions by replaying the data from these log files into the database.

Circular logging overwrites and reuses the first log file after the data it contains has been written to the database. In Exchange 2000 Server, circular logging is disabled by default. By enabling it, you reduce drive storage space requirements, but without complete transaction log files, you cannot recover anything more recent than the last full backup. Therefore, in a normal production environment, circular logging is not recommended.

Disclaimer:

All solutions advised by Backup-Connect International are based on general problem analyses. It can be possible that for a specific reason the setting are as they are and changing them can result in operational problems. Backup-Connect International does not take any responsibilities for the changes advised. If you have any doubt about changing the settings, please advice your IT administrator or IT supplier for consult.

* Source: Microsoft

Copyright notice

This document was written by Backup-Connect International. Backup-Connect’s intellectual property rights apply to the contents of this document.

303341     การทําไม้     Logging

การทํ าไม้เบื้องต้น เทคนิคและอุปกรณ์ใช้ในการล้มไม้และการตัดทอนไม้ วิธีการชักลากไม้ตอนป่า การขนส่งไม้ระยะไกล ความปลอดภัยในการทํ าไม้ และเออร์โกโนมิคส์ในงานด้านการทํ าไม้

(Introduction to logging, techniques and equipment used in felling and bucking, terrain transportation, long distance transportation safety and ergonomics in logging)

(303341 มหาวิทยาลัยเกษตรศาสตร์)

303342     การทําไม้ภาคสนาม I     Field Logging I

ฝึกปฏิบัติการล้มไม้ ทอนไม้ ชักลากไม้ด้วยแรงงานสัตว์ ชักลากไม้ด้วยกํ าลังเครื่องจักรกล และการชักลากไม้ด้วยรถยนต์ และการซ่อมบํ ารุงเครื่องจักรกลในการทํ าไม้

(Field practice in felling, bucking, animal skidding, power skidding, truck hauling and maintenance of logging machines.)

(303342 มหาวิทยาลัยเกษตรศาสตร์)

303441     การขนส่งในการทําไม้     Logging Transportation

รูปแบบการขนส่ง การชักลากไม้ด้วยแรงคน การชักลากไม้ด้วยแรงงานสัตว์ รถแทรกเตอร์กสิกรรม รถสกิดเดอร์ รถแทรกเตอร์ตีนตะขาบ การขนส่งทางรถยนต์ ทางรถไฟ ทางนํ้ า การเลือกวิธีการขนส่งที่เหมาะสม การคํ านวณค่าใช้จ่ายในการขนส่ง

(Modes of logging transportation, human power skidding, animal skidding, skidding by farm tractor, skidders and crawler tractor, road transportation, rail transportation, water transportation, choices of appropriate transportation methods, cost calculation of transportation.)

(303441 มหาวิทยาลัยเกษตรศาสตร์)

303442     การทําไม้ภาคสนาม II     Field Logging II

ฝึกการศึกษาเวลาการทํ างานและคํ านวณหาค่าใช้จ่ายใน การล้มไม้ ทอนไม้ การชักลากรวมกอง โดยแรงงานสัตว์ โดยกํ าลังเครื่องจักรกลและชักลากโดยรถยนต์

(Field practices in time studies and cost calculation of felling bucking, animal skidding, power skidding and truck hauling.)

(303442 มหาวิทยาลัยเกษตรศาสตร์)

303444     แผนการทําไม้     Logging Plan

ระบบการทํ าไม้ต่าง ๆ การเลือกระบบการทํ าไม้ ปัจจัยที่มีผลต่อการเลือกระบบการทํ าไม้ การเลือกอุปกรณ์ในการทํ าไม้ ค่าประเมินผลผลิตของอุปกรณ์ในการทํ าไม้ การคํ านวณค่าใช้จ่ายในการทํ าไม้ ผลกระทบของการทํ าไม้ต่อสิ่งแวดล้อม กรณีศึกษา

(Logging systems, selection of logging systems, factors affecting selection of logging systems, selection of logging equipment, production estimates and cost calculation of logging operations, impact of logging on environment, case studies.)

(303444 มหาวิทยาลัยเกษตรศาสตร์)

303445     การวางแผนและควบคุมผลผลิตในการทําไม้     Logging Production Planning and Control

การเตรียมเกณฑ์มาตรฐานในงานทํ าไม้ ปัจจัยที่มีผลต่อผลผลิตและค่าใช้จ่ายในการทํ าไม้ การวางแผนและควบคุมผลผลิตในการทํ าไม้ การทดแทนเครื่องจักรกล และการคํ านวณค่าใช้จ่ายการควบคุมสินค้าคงคลัง

(Standards preparing in logging, factors affecting production and costs in logging, production planning and control in logging, machinery replacement and machine rates, inventory control.)

(303445 มหาวิทยาลัยเกษตรศาสตร์)

• Fewer blisters.

• No slogging through mud to get to work. All I have to do is kick piles of dirty socks, pizza crusts and newspaper clippings away from my desk chair. I don’t even need boots for that, most of the time.

• I’m only responsible for my own limbs.

• I don’t have to live up to Paul Bunyan’s standards. I only have to keep up with Xi Xue or Dawn Yang. Who? Exactly.

• We both use bull lines, but mine don’t hurt my shoulders.

• The only rivers involved in my work are Riverdance, River Phoenix, and YouTube videos of funny ways people fall out of boats.

• Bears don’t try to eat me—or my lunch—for lunch.

• I’m not required to wear plaid shirts, which is good as they make my neck look fat.

• No guilty loss of sleep due to clear-cutting virgin old-growth forests.

• I’m not called wood hick, river pig/hog/rat, or catty-man—at least to my face.

• I can work year round rather than seasonally. And if I don’t feel like working, I can cruise over to YouTube and find videos of extreme shepherding; I can close my eyes and memorize a page in my Urban Dictionary; or I can vote on entries from My Life Is Average.

• I only have one job title and it’s not whistle punk, chaser, high climber, choker-setter or tie hack.

• Blogging isn’t voted one of the worst, most dangerous jobs. Although time will tell.

• No scooping up after Babe, the Blue Ox.

On the other hand, there are no chainsaws, log rolling, or flumes for bloggers. And no BloggerJack Picnics where we compete in various bloggy events. There’s no jaunty Monty Python song about me, and I’ve never seen a school Blogger mascot.

Hmm. Maybe I should look into being a logger instead. After all, they’re practically required to eat loads of flapjacks and wear those cool suspenders. Besides, I’d probably look awesome in a beard. As long as it’s not plaid.

Do you think being a blogger is better than being a logger?

I’m sorry I’ve been so lacking in interesting things to say.  At the moment I’m just showing up to work and trying to write a business plan.  I’m doing a slight re-write of my Nicholl Script, “Bible Con”.  I’m hoping to have it and a new script ready to send to Nicholl this year.

So, I dunno, not a lot going on.  I’m about to start working on editing a short, but I haven’t actually started yet.  I spend a lot of time trolling the internets for jobs.  Yeppers.

Too Cute