text:
If you haven't seen enough deals yet then here are a few more that you can grab at ShopRite starting Sunday 10/9! You can get a Big Pack of Huggies Diapers for only $8.99 plus you can get FREE Wipes! You can also grab Honey Bunches of Oats and Fruity Pebbles Cereals for only $.68 each!
At ShopRite (starting 10/9):
BUY ONE HUGGIES LITTLE SNUGGLERS OR LITTLE MOVERS BIG PACK – on sale $17.99 *shelf price $23.99*
BUY THREE HUGGIES WIPES – on sale $1.66 *shelf price $1.99*
Get $5 Catalina when you buy $25 worth of Huggies Products
use one $2.50/1 Huggies Little Snugglers, Little Movers or Huggies Overnites Diapers SS 9/25
use one $2/1 Huggies Diapers ShopRite eCoupon
use three $.75/1 Huggies Wipes 56 ct or larger SS 9/25
Price at register: $13.99 but receive $5 Catalina
Net Price: $8.99 + FREE Wipes!
BUY TWO HONEY BUNCHES OF OATS CEREALS – on sale $1.99
BUY TWO FRUITY PEBBLES CEREALS – on sale $1.99
Get $.50/1 Post Pebbles Cereal Checkout 51 Offer
Get $.50/1 Post Honey Bunches of Oats Cereal Checkout 51 Offer
Get $.25/1 Cereal, Any Brand Ibotta Offer
use one $1/2 Honey Bunches of Oats printable coupon (preclipped)
use one $1/2 Honey Bunches of Oats Cereal ShopRite eCoupon
use one $1/2 Pebbles Cereal printable coupon (preclipped)
use one $1/2 Pebbles Cereal ShopRite eCoupon
Price at register: $3.96 but receive $1 Checkout 51 and $.25 Ibotta deposits
Net Price: $2.71 ($.68 each!)
Thanks LRWC
Extreme Couponing Tip: You can usually get two prints of most internet coupons. To find them in the easiest possible way, use our preclipped links that take you right to the coupon. Then come back and click the same link to get your 2nd print. This will save you the time spent searching for the coupon.
Never miss another hot coupon, deal or freebie again! "Like" Couponaholic .NET on Facebook, Follow us on Pinterest, Follow us on Twitter, Follow us on Instagram or Subscribe to our Daily Email Newsletter!


text:
The DRACONERIUM HOTEL is a modern design hotel, built following new standards of comfort, efficiency and functionality, combined with incomparable hospitality and above all with particularly interesting prices. The hotel is situated at the entrance of Dronero, at the beginning of the Valley Maira. Draconerium Hotel is an ideal place for a pleasant and quiet stay, both for holidays and for work.
A precious mixture of elegance and discretion, immersed in an extraordinary setting that makes it particularly suitable for short or long stays.
Tutti i Commenti sull'Hotel Draconerium - Scrivi un Commento
Tutte le Offerte dell'Hotel Draconerium
Tutte le News »
Happy Bokeh Thursday!
HOTEL DRACONERIUM - Hotel Dronero Valle Maira CUNEO
Via Cuneo, 38 - 12025 Dronero CUNEO - Tel +39 0171904006 - Fax +39 0171909268
P.IVA 03147320042 - C.F. 03147320042 - Mail: email@example.com
Area Operatori - Credits: GEM Communication Dronero Cuneo

subset: commoncrawl


text:
Tree Service - Tree Trimming - Tree Removal - Stump Removal
Tree trimming, tree removal, stump removal, line clearing, and complete tree service requires a knowledgeable, licensed, bonded, and insured arborist, like Tom Day Tree Service. Protecting your trees and your property is our main concern.
Professional Tree Care Since 1974
Emergency Tree Service Available
"Healthy Trees for Generations To Come."
State Contractors License # 746006
Why Trees Need Routine Care
Trees do not live forever. Trees require care to reach their full life span. While a tree may be strong and tall, keeping them alive is a fragile endeavor. The "skin" of a tree lay just below the protective bark. One can think of it as a glove over the entire branch, trunk, and root system. It is only 3 cells thick. Very fragile. This "skin" is the only living tissue of the tree. Damage a significant portion of it, and the tree is in danger of dying.
Further, each branch of a tree corresponds to a root. Kill that root and no nourishment goes to the related branch, and it will die.
Proper tree maintenance includes appropriate nourishment, and protection from disease and insect infestations. Improper pruning techniques can severely damage trees, leaving them vulnerable to weaknesses, which in turn can lead to an unsafe environment for property and people. Trees should be inspected, pruned, and nourished regularly.
Want to have healthy trees for generations to come? Tom Day Tree Service will help you manage your tree assets for the long term. We've been doing this, right here, since 1974.


text:
Your Pet's Wellness is a modern veterinary hospital with two locations on the north side of Chicago. We are proud to have had significant growth since first opening our doors in 2011, and are now ready to add another Associate Veterinarian to our team!
We are currently a 3-doctor practice, with an additional part-time Feline Internal Medicine Specialist. Our flagship hospital is located in Bucktown, plus we have an additional clinic in Logan Square that offers supplementary services of doggy daycare/boarding, grooming, and retail. We also perform housecalls.
Your Pet's Wellness is an excellent place to practice small animal veterinary medicine! We pride ourselves on the quality of our veterinary visits, which we facilitate by allowing one-hour appointments for each new client and a minimum of 30-45 minutes for all other visits. Our state-of-the-art equipment includes 3 Abaxis VS2s, CBC, iSTAT, digital x-ray, digital dental x-ray, ultrasound, and therapy laser. We also have the capability to perform stem-cell and PRP therapies. Moreover, all this technology is supported by some of the very best veterinary technicians in the city! We have recently implemented an extensive tiered technician training program to ensure that all support staff members fully contribute to the medicine. We are a true team environment! Plus, we have excellent clientele who are able and willing to treat their pets like family members!
Associate Veterinarian will perform the following scope of work:
Prospective Students |
Current Students |
Alumni |
Veterinarians |
Reporters |
College Community |
© 2014 Cornell University College of Veterinary MedicineIthaca, New York 14853-6401
Please report problems with this page to the webmaster.
Cornell University | Contact |
Privacy Policy
follow us on:


text:
|2004N-0115 - Prescription Drug Importation; Public Meeting
|FDA Comment Number :
|Submitter :
|Mr. Andrew Ysiano
|Date & Time:
|05/18/2004 11:05:59
|Organization :
|Citizens Against Lawsuit Abuse
|Consumer Group
|Category :
|Issue Areas/Comments
| Citizens Against Lawsuit Abuse, San Joaquin County Chapter is opposed to having prescription drugs coming into the U.S. that could potentially harm patients. This raises the risk of patients getting the wrong medicine and then no one is going to take responsibility. We support the safety of U.S. citizens, not put them at more risk.


text:
Zillebeke and Surrounding Area
The village of Zillebeke is located about one and a half miles south-east of Ypres, and there is a lake of the same name nearby. There are many sites of interest to be seen, both in the village and also in the surrounding area - so this page covers locations for some distances in all directions around the village. To reach the village, follow the N8 from Ypres (towards Hooge and Menen), and go right at the roundabout where it joins the N345 and N37, following the sign for Zillebeke. (This roundabout is on the location of what was the infamous 'Hellfire Corner').
Following this route, on the northern outskirts of the village are two cemeteries. The first is Perth Cemetery (China Wall), which is located on the left hand side of the road.
Perth Cemetery (China Wall) perhaps between the Wars. Photo: NELS
The words 'Perth Cemetery' are inscribed on the left of the entrance gateway, whilst 'China Wall' is inscribed on the right. The latter name comes from a communication trench which ran close by known as the Great Wall of China, whilst the name Perth probably originated with the 2nd Scottish Rifles, who took the cemetery over from the French in June 1917. It was also known during the war as Halfway House Cemetery. This is a large and intersting cemetery, and well worth spending some time on.
Just inside the cemetery is an old Belgian Police notice, which I have not seen in other cemeteries in the area. In three languages, this sets out a Belgian Royal Decree of regulations for Commonwealth military cemeteries, dated 23rd of June 1987. This also quotes the original September 1917 decree ceding land in perpetuity for military cemeteries, and a further agreement signed in July 1951.
The notice describes various activities which are forbidden within war cemeteries, including putting up notices on the walls or fences, climbing any wall or structure and organising political meetings. It also demands respect for the cemeteries, and bans any activities "incompatbible with the peace and dignity of the site or with the respect due to the dead". Those who infringe this, it cautions, may be imprisoned for 8-14 days or fined between 26 and 200 francs (although I am not sure what this would now be in Euros!).
Perth Cemetery (China Wall) stretches a long way back from the road and contains over 2,700 burials, about half of which are of unidentified soldiers. During the war, it was only used for around five months by the British, and there were only about 130 graves (within Plot 1).
Plot 1 (with the original wartime graves) is located at the back. These early burials have an irregular layout, but part of Plot 1 is of graves in regular rows. A photograph taken shortly after the War shows these graves, and this can be compared with todays view immediately below.
Perth Cemetery (China Wall) shortly after the War Photo: Van Winsen
After the Armistice, the cemetery was greatly enlarged by the concentration of graves, with more than 2,500 brought in from at least 28 smaller cemeteries and the surrounding battlefields. The original French graves were removed after the war. It would seem that the early photograph above predates the completion of the cemetery, as plots 9-15 to the right hand side do not appear to be present (a fence and a small shed are visible).
Two crosses in the early photograph show names that can be read; Private E. Blick and Lieutenant F.E. Foers.
The original cross marking Private Blick's (real name Lloyd) grave. Photo: Van Winsen
There must be an interesting story behind Ernest Blick. This name still appears on the headstone, but it also records that this was an alias, and his true family name was Lloyd. Ernest Lloyd was born in Cheltenham England in about 1875, but it was the Canadian Expeditionary Force he enlisted in on the 5th of July, 1915. He died less than a year after he enlisted. He gave his next of kin as his sister, Mrs. Louise Fisher, of Cheltenham. However, the CWGC records that he was the husband of Ellen Lloyd, also of Cheltenham. He may have moved to Canada beforfe the War, returned to England to visit family and married. Perhaps there is another explanation behind why he used an alias and enlisted in Canada.
Whatever the story of his life, Ernest Lloyd, serving as Blick with the 43rd Canadian Infantry Battalion, was killed on the 3rd of June 1916, aged 41. The unit's war diary records that around midnight on the 3rd the battalion moved up to Zillebeke and that 6 soldiers were wounded. Blick/Lloyd may have been one of these; although no men were reported as killed that day, perhaps he died from his wounds shortly after (although the original cross reads "Killed in Action").
Headstone commemorating Private Blick (Lloyd) today
Whilst the original grave marker for Blick/Lloyd is non-standard, and probably an original war-time cross, the one to the right marking Lieutenant F.E. Foers grave in the early picture is a standard IWGC wooden cross, but with a personal marker attached to it's top.
The original cross marking Lieutenant F.E. Foers' grave. Photo: Van Winsen
Second Lieutenant Frank Everest Foers enlisted in the ranks on the 29th of October, 1914. He was killed in action by machine gun fire on the 20th of September, 1917. The grave was originally recorded as "number 367", but is now Plot 1, Row G grave 47. His file at the Australian National Archives records that he was buried at Perth Cemetery "beside China Wall trench". He had served previously at Gallipolli, where he had been wounded in the left leg on Sunday August the 8th 1915, at Lone Pine.
The marker on top of the standard IWGC cross was put there by his brother, Roy Valentine Foers, who also served with the AIF, enlisiting in the Artillery after his brother was killed but not arriving on the Western Front until 10 days after the Armistice. Roy died in 1946.
In 1930 Frank Foers' father paid for a copy of the register of the cemetery where his son was buried. One imagines in those days it would have been very unusual for the family to able to visit France and see the grave.
The original photo of the cemetery showing Frank Foers' grave must have been taken prior to 1925, as in that year the Officer in Charge of records wrote to Walter Foers to report that the permanent headstones were being put up in Perth Cemetery (China Walls).
Today, the graves are all marked with the standard headstones. Although Foers grave appears to be positioned forward of the others in the row in the early photograph, today they are all in a straight line. Sadly, at the time I took these pictures, the inscription on Foer's headstone was so faint that the words could hardly be read, and I was unable to take a photograph that showed enough detail to add to this page.
The wartime burials in Plot 1 at Perth Cemetery (China Wall)
Located between the graves of Blick/Lloyd and Foers is the grave of a Victoria Cross winner - Second Lieutenant Frederick Birks, of the 6th Battalion AIF. In the early photograph shown above, Second Lieutenant Birks' grave is to the left of the one with the wreath hanging on it. It is completely unadorned and with no special markings although there is an 'In Memoriam' wreath which may be in front of the grave.
Frederick Birks was commissioned as a Second Lieutenant on the 26th of April, 1917. He had enlisted on the 18th of August, 1914, and sailed from Australia on the Wiltshire on the 19th of October 1914. However, this was not the first time he had crossed the ocean, as he was born in Buckley near Chester in 1894, and his mother (listed as his next-of-kin) lived there until she died in late 1917. Frederick had two brothers, Samuel and John, and four sisters, Polly, Beatrice, Emily and Martha. There may have been a romantic interest in Australia, as a Miss Suzy Gelven of Langs Bay wrote twice to the authorities in 1917, concerned that she had not heard from Fred. Her letters date from well before he was killed however.
Frederick Birks was a Labourer, and aged just over 20 when he enlisted. He is described as having a dark complexion, hair and eyes. He trained at Broadmeadows Camp near Melbourne, which had only just been established and was then a "spartan and tented camp", and served initially as a Private with No. 2 Field Ambulance. He was wounded at Gallipolli, and later promoted, first to Lance Corporal and then to Corporal. He then served in France, and in October 1916 was awarded the Military Medal for "bravery in the field". He was posthumously awarded the Victoria Cross, for his actions during an attack on Glencourse Wood (about two miles from here) on the 21st of September, 1917. His official citation reads:-
For most conspicuous bravery in attack, when, accompanied by only a corporal, he rushed a strong point which was holding up the advance. The corporal was wounded by a bomb, but 2nd Lt. Birks went on by himself, killed the remainder of the enemy occupying the position, and captured a machine gun. Shortly afterwards he organised a small party and attacked another strong point which was occupied by about twenty-five of the enemy, of whom many were killed and an officer and fifteen men captured. During the consolidation this officer did magnificent work in reorganising parties of other units which had been disorganised during the operations. By his wonderful coolness and personal bravery 2nd Lt. Birks kept his men in splendid spirits throughout. He was killed at his post by a shell whilst endeavouring to extricate some of his men who had been buried by a shell.
Information in his service record at the Austalian National Archives confirms that he was killed by a shell in the morning of the 21st, whilst standing in an exposed position trying to help those who had been buried by the shell.
His headstone today has the symbol of the Victoria Cross engraved on it, and in June 1924, the Imperial War Graves Commission wrote to Australia asking the Base Records office of the AIF to check with Frederick Birks next of kin as to whether the proposed design met with their approval. Their letter was returned to London, suggesting they contact the next of kin (Frederick's elder brother, Samuel) directly, as he lived in Buckley. Their mother, Mary Birks had died aged 59 towards the end of 1917, her own death perhaps hastened by that of her son in September.
The grave of Second Lieutenant Frederick Birks, VC, MM
There are fields to the left and the rear of the cemetery, with a new brick built office building to the right. In row 6A, a single headstone marks the burial of ten unknown soldiers (picture below).
Headstone commemorating ten soldiers of the Great War
At the front right of the cemetery are special memorial headstones arranged in an extended loop. There are three larger memorial blocks which give more information. These special memorials commemorate 108 soldiers who were buried in a number of other cemeteries, including Wallemolen German Cemetery (near Passchendaele) plus a number of other German cemeteries and also Trench Railway Cemetery and Durham Cemetery (both were in Zillebeke, the latter quite near to here). There graves were destroyed by later fighting, so each man is commemorated by a special memorial stone in this loop.
The loop of special memorial headstones at the front of the cemetery
It must have been doubly hard for the families of those who died to visit in these situations; to see a 'headstone' with their loved one's name on, but knowing that this did not in fact mark the grave. Some of the inscriptions are especially moving, for example that on Private B. Harding's grave reads "He nobly fell for the love of all. From his broken-hearted mother". As these soldiers do have headstones naming them, their names do not appear on the Menin Gate.
Also of interest is the fact that several men who were executed during the Great War are buried here.
Travelling a little further south, Tuileries British Cemetery can be found up a small grass track off to the right of the road. The name means tileworks, and comes from the works that were located near here before the war. The cemetery was started in 1915, but later on many of the graves here were destroyed by shelling. Only the locations of 26 graves are still known, and these are in rows A-D at the front. Sixteen of these are the graves of unknown soldiers.
The known graves at Tuileries British Cemetery
There are special memorial headstones for the 69 Commonwealth and two French soldiers whose graves were destroyed, and these are arranged around the edges of the cemetery, with the Cross of Sacrifice thus standing in a lawned area in the centre.
Special memorial stones line the edges of Tuileries British Cemetery....the original graves were destroyed by shelling
Zillebeke Village
Travelling a little further south, you reach the centre of the village. There are war graves to be found in Zillbeke Churchyard, and these are of great interest. The church is located to the left of the road as you travel south.
The CWGC graves are at the front left of the church yard. There are many early casualties of the war buried here, with several members of the aristocracy among them. Very unusually, there are two non-standard headstones to be seen here. They can just be picked out among the standard headstones in the general views below.
Second Lieutenant Baron Alexis George de Gunzberg was Russian born but lived in Paris. He was killed on the 6th of November 1914, serving with the 11th Hussars. The tombstone bears the imprint of the stonemason of Ypres who made it.
The tombstone of Second Lieutenant Baron de Gunzberg at Zillebeke Churchyard
The other unusual headstone here is that of Lieutenant Lee Steere, of the Grenadier Guards. The private memorial stone stands rather incongruously at the end of a short row of standard headstones.
The tombstone of Lieutenant Lee Steere, alongside standard CWGC headstones
John Henry Gordon Lee Steere died on the 17th of November 1914. The CWGC records state he was with the 3rd Battalion of the Grenadier Guards, but his headstone states the 2nd Battalion. He was aged 19, and already married when he died.
The grave of Lieutenant Lee Steere
Some of the standard headstones within the churchyard are very weathered and difficult to read. At the very front of the churchyard are two special memorials which commemorate soldiers who were buried here, but whose graves were destroyed by shellfire. They could be from two extremes of the British social spectrum before the Great War. One is Lieutenant The Honourable William Reginald Wyndham, third son of the 2nd Baron Leconfield. He joined the Life Guards in August 1914 and was killed in action on the 6th of November 1914. The special memorial next to his commemorates Private William Stewart of the Royal Scots, who died on the 16th of December 1915. Private Stewart was almost half the age of the Honourable Lieutenant Wyndham; and his inscription simply reads "There is a world above where parting is unknown". Both men were buried somewhere in this churchyard over 90 years ago, and despite their probable social differences, both made the ultimate sacrifice for their country.
One notices when walking in Flanders that shells are still recovered from the fields; remnants of the war that raged here. They are still dangerous today, and were even more so just after the war when there were far more of them and the land was being reclaimed by the locals following four years of devastation. In September 1921, a shell exploded at Zillebeke when some workmen were levelling the ground. It killed four of the Belgian workmen, injuring four others seriously.
South of Zillebeke
The road south through the village then forks to lead left or right. Following the right turn, after about a third of a mile at a T-junction is one of the Demarcation Stones erected after the war by the Touring Clubs of Belgium and France. Like many others that still remain, the carving has faded, but the outline of the helmet and the waterbottle on the side can be made out.
Two views of the Demarcation Stone at Zillebeke
In the garden of a house by this junction are the remains of what appears to be an "elephant-iron" covered bunker.
'Elephant-iron' bunker in a garden at Zillebeke
Turning left at the T-junction leads along small, but well signed roads to a place where you can park your car and walk to three isolated and peacuful cemeteries. These are close to a famous feature known as The Bluff.
A grass track leads from the small road to reach Woods Cemetery, 1/DCLI Cemetery and Hedge Row Trench Cemetery. This is quite an isolated area, but popular with walkers and families. The grass track leads straight on to Woods Cemetery, whilst another track leads off to the right to the other two cemeteries.
Sign to three smaller cemeteries near Zillebeke
Woods Cemetery is arranged with a long 'stem' leading to the Great Cross, and then a wider part fans out to the left of it. The front line was just beyond the wood, hence the irregular layout of the cemetery. It is about as remote and peaceful as can be found in this area - so many cemeteries in the Salient are now built around, but this remains in open country and woodland.
The cemetery was started by the 1/Dorsets and 1/East Surreys in April 1915 and was used until September 1917. Three RFA burials from the 12th of November 1917 are alone in a little spur leading off to the left of the larger end of the cemetery - this is described by Paul Reed in Walking the Salient as a field grave, perhaps a shell-hole where these men were originally buried. On the opposite side are the graves of two 8/Post Office Rifles soldiers, Riflemen Edwin Helps and E C Evans, killed on the 15th of December 1916.
The cemetery is on two tiers; by the Cross of Sacrifice two sets of steps lead down either side to the lower, wider part. There is an intermediate level here, with two graves on each side.
Returning along the grass track back towards the road, another track (signposted) leads uphill to 1/DCLI Cemetery (listed as First DCLI Cemetery on the CWGC website). This is a very small cemetery containing 76 graves, with no register on site. There are only four rows of graves; the three facing great cross almost exclusively of First Battalion Duke of Cornwall's Light Infantry (DCLI) men who died in May and June 1915 and are original wartime burials. They were involved in fighting at The Bluff, about half a mile south-east from here. The other row, Row D, at the back of the cemetery contains the graves of men from other units, which were brought in after the Armistice.
1/DCLI Cemetery: general view (left) and the rows of 1/DCLI men buried here (right)
The grass track continues to left of 1/DCLI Cemetery, and then leads to the right round woodland, giving good views over the surrounding area. It then runs uphill to Hedge Row Trench Cemetery. This again was an original wartime cemetery, sometimes known as Ravine Wood Cemetery. Once again, this is a small cemetery with just under a hundred buried here, men who died between March 1915 and August 1917. The register can be found in a box located on the outside edge of the left gatepost. The layout of this cemetery is unusual; the headstones are arranged around the edges (four short rows, one on each side) and in a circle around the Cross of Sacrifice. On each headstone are the words "Known to be buried in this Cemetery" - and even the headstones of unidentified soldiers have these words on them.
Hedge Row Trench Cemetery: grave locations are not known, so the 'headstones' are arranged in a circle
The reason for this is that after the burials were made the cemetery was very badly damaged by shellfire, and later the original positions of the graves could not be determined. Hence, the cemetery was designed by J Truelove in the symmetrical layout seen today; none of the headstones marking actual graves. There is an information board outside the cemetery which also explains this in Flemish and French. A truly tranquil spot, and a good place to spend a few minutes reflecting on the sad fact that the men buried here were denied actual grave markers due to the fighting that continued after their deaths.
Returning to your car, and driving back the way you came, pass the T-junction where the demarcation stone is located and continue straight on. Another small cemetery can be found down a small track leading left, downhill, to both the cemetery and a private house. This is Blauwepoort Farm Cemetery.
There is a herd of small goats in a pen in front of the cemetery, and the stone wall of the farm garden now joins directly up with the cemetery wall. On trench maps, the farm name was spelt as two words - Blauwe Poort - and at that time there was a small moat around three sides of the farm buildings.
Graves at Blauwepoort Farm Cemetery
There are 82 graves here, and the register can be found in the small arched structure to the left of the gate. The layout of graves is somewhat haphazard, indicating this is a wartime cemetery with what appear to be odd gaps between some graves. The cemetery was originally started by the French in November 1914, taken over by the British in February 1915 and used for a year or so. The French graves were removed after the Armistice. Some of them may be visible in the front left in the early photograph of this cemetery shown below, as there seem to be more graves in the first visible row than can be seen today. The photo is believed to date from the early 1920s, and there are remarkably few differences in the same view today, apart from the building of the cemetery wall.
Blauwepoort Farm Cemetery shortly after the War Photo: Van Winsen
A similar view of Blauwepoort Farm Cemetery today
Returning to the road and continuing north-west, on the left of the road is one of the larger cemeteries in the salient, Railway Dugouts Burial Ground (Transport Farm). Both names were used during the war.
Railway Dugouts Burial Ground (Transport Farm) general view (left) and special memorial 'headstones' arranged in a circle (right)
The name derives from the dugouts located in the railway embankment that was located here during the war. Siting dugouts on the side away from the Germans protected them from artillery fire. The railway still passes today, and trains can be seen rushing past the cemetery from time to time. It is a large and complex cemetery, with among other features a small lake partly in and partly outside the cemetery (shown below). There is also a circular arrangement of special memorials (shown in the photo above right) to men who were buried in Valley Cottages Cemetery and Transport Farm Annex whose graves were destroyed in fighting during the war.
Trains still pass the cemetery, and a lake is among the features of this large cemetery
The cemetery was started in April 1915, and must have been quite large by the end of the war. There are just under 2,500 buried or commemorated here, only around 400 of whom were brought in after the Armistice. As an Advanced Dressing Station was located here for part of the war, the large numbers are not surprising. Many of the original burials would be of those who survived long enough to be sent or brought back from the front line, but who succumbed to their wounds at the ADS.
The picture below shows the cemetery as it appeared just a few years after the War, probably in the early 1920s. It is possible to determine the spot the photo was taken from, which is from the left rear of the cemetery, between plots 6 and 7.
Early picture of Railway Dugouts Burial Ground (Transport Farm). Photo: Van Winsen
The same view today
The layout of the graves can be matched; the four headstones in the foreground are to men of the 68th and 69th Machine Gun Corps who died on the 7th of January 1917. They are Privates G Brown (a Military Medal winner) and Charles Leggett, Company Sergeant Major John Bunning and Lance Serjeant R Hamlet. The early photo is captioned 'Transport Farm', and as stated above the two names were both used for the cemetery. On the early photo, one grave, the cross apparently in between rows B and C, seems to have been moved when compared with today as the rows are straight.
There is one German headstone in a the far right corner by itself, with three names on it. Just inside the left entrance, and to the left of it are four Indian graves. The cemetery wall behind these was damaged when I was last there in May 2006. There is also a large double circle of special memorial stones around the Great Cross, commemorating those known to be buried here but where the location of the grave is no longer known. Many of these may relate to an incident in the summer of 1917, when many graves had not been marked when they were destroyed be shelling.
Graves at Railway Dugouts Burial Ground (Transport Farm)
On the opposite side of the road from the cemetery, a well-preserved bunker can be seen. Just a little to the south-east of it was Transport Farm Annex Cemetery, which contained 27 British burials. These graves were moved after the Armistice to Perth Cemetery (China Wall) - see above.
Bunker near Railway Dugouts Burial Ground (Transport Farm)
Just before Railway Dugouts/Transport Farm Cemetery, a road leads off to the north, signposted to a restaraunt. This road leads past Zillbeke lake and it is possible to walking on paths round the lake. During the war the path by bthe lake was a route used by the troops to reach the front line.
Sources & Acknowledgements
Australian War Memorial website
Commonwealths Wargraves Commission website
Great War Forum
Major & Mrs Holt: Battlefield Guide to the Ypres Salient
National Archives of Australia website
Paul Reed: Walking the Salient
Michael Scott: The Ypres Salient
The Times archives


text:
Upon hearing about the government sanctioning Sharia law in the United Kingdom, I was immediately concerned that western law was being subverted in an ally country with whom we share a unique history. There are two levels on which there might possibly be concerns. The first possible concern arises when one compares Sharia law to a traditional, Western sense of justice. The second possible concern arises when this event is viewed from a historical perspective. Upon thinking through these possible concerns, I believe that the first one raises interesting questions that Christians especially ought to consider and the second may actually be troubling.
In his speech on the rise of Islam in the United Kingdom and the coming sanctioning of Sharia law, Archbishop Rowan Williams best draws out the nature of the first concern. Williams said,
And what most people think they know of sharia is that it is repressive towards women and wedded to archaic and brutal physical punishments; just a few days ago, it was reported that a 'forced marriage' involving a young woman with learning difficulties had been 'sanctioned under sharia law' – the kind of story that, in its assumption that we all 'really' know what is involved in the practice of sharia, powerfully reinforces the image of – at best- a pre-modern system in which human rights have no role.
Off-the-hip criticisms of sharia law, especially in the media, will tend to focus around the easiest elements to critique. Namely, criticism will focus on the areas where sharia law tends to most barbarically separate from traditional, Western ideas of justice. The contrast between sharia law and Western law is especially easy to notice when one compares the rights of women within the two systems. In an election year where Hillary Clinton was almost a presidential nominee for one ticket and Sarah Palin is the Vice-Presidential nominee for another, it seems pitiful that there is still a legal and cultural tradition where a man can divorce his wife via text message while the wife cannot divorce her husband save for impotence or his extended absence.
Nonetheless, while we believe in the rights of women we simultaneously highly value cultures, especially minority cultures, and their traditions. We value liberty and the freedoms of those with religious beliefs. We desire to liberate people from oppressive systems, but we simultaneously believe that we liberate people from oppressive systems so that they may live freely according to their beliefs so long as they are not openly subversive to the state. At the heart of these beliefs is an interesting tension between free expression and how one chooses to express himself/herself freely. At the center of the tension are questions about the nature of law which are especially important for Christians to consider.
Continue reading East Meets West: Sharia Law Sanctioned in UK


text:
How to Buy
Solutions Overview
This script is Copyright (C) 2011-2015 Tenable Network Security, Inc.
Synopsis :
The remote Windows host is affected by a code execution vulnerability
in the Windows Backup Manager.
Description :
The remote Windows host contains a version of the Windows Backup
Manager that incorrectly restricts the path used for loading external
If an attacker can trick a user into opening a specially crafted
Windows Backup manager file that is located in the same network
directory as a specially crafted dynamic link library file, he may be
able to leverage this issue to execute arbitrary code subject to the
user's privileges.
See also :
Solution :
Microsoft has released a patch for Windows Vista.
Risk factor :
High / CVSS Base Score : 9.3
CVSS Temporal Score : 7.7
Public Exploit Available : true
Family: Windows : Microsoft Bulletins
Nessus Plugin ID: 51454 ()
Bugtraq ID: 42763
Get Nessus Professional to scan unlimited IPs, run compliance checks & more
The cookie settings on this website are set to 'allow all cookies' to give you the very best website experience. If you continue without changing these settings, you consent to this - but if you want, you can opt out of all cookies by clicking below.


text:
Tweets from @TBHomeTeam/writers
MORE from our HomeTeam writers.
Tue. May 7, 2013 | John C. Cotey | Email
CLEARWATER — Nate Reed struck out the side in the fourth inning, then homered to tie the score and struck out the side again in the fifth.
For a second, the Calvary Christian ace looked invincible.
Then the sixth inning happened.
A one-out error started a string of very fortunate events for Clearwater Central Catholic, which seemed to finally figure out Reed with three consecutive RBI singles to turn a pitcher's duel into a 7-1 victory in a Class 3A region semifinal.
The sudden turn of events sends CCC (25-4) to West Palm Beach King's Academy Friday for its sixth region championship game since 2001, with a trip to state on the line.
After retiring his 10th straight hitter to open the bottom of the sixth, Reed (8-4) got Brendan Overton to hit an easy groundball to short.
But the throw sailed into the Calvary Christian dugout, leaving Overton at second.
CCC starting pitcher David Paul was walked intentionally, before catcher and No. 5 hitter Andrew Mink nudged a Reed offering into short rightfield to score Overton and break a 1-all tie.
But the Marauders weren't done. Andrew Murphy was next, with a two-run single, and pinch-hitter James Hancock Jr. followed with another RBI single.
Another throwing error scored two more runs, giving Paul all the cushion he needed.
"We caught a break, that kind of opened the door," CCC coach Todd Vaughan said. "My guys just took advantage and got some hits. Mink was huge for us. The at-bats he had before that didn't look too good, but he did what we needed him to do."
As did Paul, who allowed just three hits and struck out nine in improving to 9-0 on the season.
Reed's homer in the fifth that tied the score was the first ball the Warriors (22-8) hit out of the infield, and Jake Richardson's single the next inning was the only other one to find the outfield.
Paul bore down after giving up the home run, retiring nine of the last 11 batters he faced.
"Well, obviously it got in my head a little bit but I knew I had to keep pitching," Paul said. "I knew one run wasn't going to beat a team like that and we had to score more runs, and they were going to need more than one run and I wasn't going to let that happen."
8A: East Lake stymied by Durant's Danish
EAST LAKE — Never mind what may have been said over social media, or from the aluminum bleachers, or from the fences along the foul lines, or even in those fleeting moments between fastballs.
Here's what was said when the game was all over, when Tyler Danish had done what he always does from the mound and pitched Durant to a 3-0 victory over East Lake in their Class 8A region semifinal.
"He's as good as it gets," East Lake coach Dan Genna said.
"He's the best pitcher we've faced all year," East Lake second baseman Doug Rovello said.
"They said, 'They're ready for Danish,' " Durant coach Butch Valdes said. "You haven't seen Danish. No one has seen Danish. This kid is special. He really is."
Danish pitched his eighth complete game of the season Tuesday, allowing two hits, walking three and striking out 14 in a masterful performance against an East Lake lineup that was averaging more than six runs per game.
Durant (23-5) advanced to its second region final in three years.
Standing in the Cougars' way was East Lake (24-4), which had won eight straight games and eagerly awaited a rematch following its 3-0 loss to Durant in the region quarterfinal last season.
The Eagles had managed to avoid Danish in last year's game and still failed to produce any offense against then-senior starter Trey Oest.
This time, they weren't so lucky.
Danish and the Cougars said there was a little more trash talk and banter than in previous games.
"I tried not to notice it," Durant second baseman Jared Donini said, "but there was smack-talking the whole time."
Indeed. There was a lively crowd at Lee Byers Field, with both the home and visitors bleachers filled with fans and nearly that many lining the fences along the field — to say nothing of the crowd of major-league scouts behind home plate.
Rovello, who had the only two hits against Danish, said he and his teammates had encouraged their fans to turn out for the game.
"We just promoted it like a fight," he said.
The teams didn't strike many blows in the first four innings, as East Lake sophomore starter Ryan Wall nearly matched Danish from the mound. The game was scoreless until only a single out remained in the top of the fifth.
It was then Durant centerfielder Garrett Wright delivered the knockout shot, with runners at first and third base.
Wright singled to shallow left, where the Eagles' outfielder failed to cleanly field the ball and Donini seized upon the opportunity to score from second.
"When you've got Danish in the mound, we know that if we score one run a lot of pressure is taken off," Wright said. "Then it's on him."
The Cougars added two more runs in the sixth, but Danish gave East Lake a sliver of hope by issuing two walks in the bottom of the inning.
With runners at second and third, a newly energized home crowd and cleanup hitter Keegan Maronpot at the plate, the Eagles finally were in position to score — something only one other team (Newsome) had managed all season.
Danish responded with a three-pitch strikeout to end the inning.
"I knew the streak was still there," said Danish, who kept his ERA at 0.00 for 2013. "But I got backed down into a corner and responded like I have all year."
6A: Osceola can't slow King bats
SEMINOLE — For four innings Tuesday, King and Osceola were locked in a tight, low-scoring game.
That all changed in the fifth inning.
The Lions' offense came unhinged. Seemingly every batter was able to hit the ball in the gaps. And the runs came in bunches. By the time the top half of the inning ended, King sent 15 batters up, recorded 10 hits and scored 11 runs.
That outburst was all King needed in a 12-0 victory that was called after five innings because of the 10-run mercy rule. The Lions (24-3), who have won 15 straight, will host Mitchell in Friday's Class 6A region final.
"I hate to say it, but we were pretty confident," King coach Jim Macaluso said. "We have a good offensive club, and we started to hit balls that were finding the gaps."
It didn't start out that way. Osceola starter Justin Kremer was keeping the Lions at bay, holding them to three hits through four innings.
Trouble was, the Warriors could not do much on offense, either.
Brandon Caples, King's No. 2 pitcher, allowed just one hit and walked one batter in five innings to improve to 9-0. His performance was big considering the Lions were able to save ace Brett Morales for Friday's game.
"This wasn't us gambling and trying to save our ace, though," Macaluso said. "We have all the faith in Brandon. We've stayed with the same rotation and started each pitcher every other game this year."
Caples was able to cruise by, relying on his off-speed pitching, particularly his curveball.
"I had a little bit of nerves, but once we got a run they all went away," Caples said. "I got stronger as the game went on."
He got all the run support he needed in the fifth. Kevin Buckley, Sey Juan Lawrence and Bubby Terp each had two hits in the inning and scored twice.
The Warriors, meanwhile, went through three pitchers. All Osceola coach Stefan Futch could do afterward was shake his head.
"I thought we played the best with what we had," Futch said. "We were right there for four innings, and I was hoping maybe we could squeeze a run in and stay in it. But give (King) credit. They swung the bats real well in that fifth inning. It seemed like every batter was getting a hit."
5A: Rocky start grounds Falcons
DUNEDIN — For Jesuit coach Richie Warren, Tuesday night's Class 5A region semifinal against Dunedin was like old times. During the past three weeks, the Tigers lost two of five games and didn't score more than five runs in any of them.
But the bats came alive against the Falcons. Jesuit erupted for 16 hits, eight of them for extra bases, in an 11-1 win.
"Sometimes box scores are misleading," Warren said. "You only score three runs but you hit the ball right at people. Tonight was a step in the right direction. It's something we've been looking forward to. It's like it was earlier in the year when we were beating teams by 10 runs."
Jesuit (26-2) wasted no time getting to Dunedin starter Alex Hart. Vincent Miniet led off with a home run to left-centerfield, and it was downhill for the Falcons (18-10) from there.
One out later, Adrian Chacon doubled and Leland Saile walked. With two outs and two on, Daniel Portales tripled home two runs to make it 3-0. In the bottom of the first, Jesuit starter Jordan Parnell needed only four pitches to get three outs. It was that kind of night for Dunedin.
"What hurt was that after they get those three runs, we come back with a four-pitch bottom half," Dunedin coach Tom Hilbert said.
"We thought that if we could get off to a good start, we'd have a chance. Certainly, we had to play a perfect game. We didn't do that. A lot of that is because they are such a good team."
In the second inning, Spencer Trayner had an RBI single and later scored on a Kellen Brown throwing error to first that made it 5-0 Jesuit.
Dunedin had its best chance to cut into the lead in the third. The Falcons loaded the bases with one out. Warren removed Parnell for relief pitcher Ronnie Ramirez.
Ramirez walked Brown to force in a run. But the rally was killed when Aaron Chesson lined to rightfielder Saile, who threw out Trever Jensen at home for the third out.
Jesuit tacked on two runs in the fourth, highlighted by a homer from Evan Cannan, and another in the fifth to take a commanding lead.
And just for good measure, Saile hit a three-run homer in the sixth to make it 11-1.
"We've been hitting the ball right at people and not catching any breaks," Trayner said. "Tonight we caught the breaks. We were all seeing the ball well."
Trayner was 3-for-5 with an RBI, Miniet 2-for-5, Chacon 3-for-5 with an RBI and Saile 2-for-4 with three RBIs.
Four Jesuit pitchers held Dunedin to seven hits.
2A: Canterbury falls just short
Canterbury could not make it two straight against Sarasota Christian, falling 6-5 in a Class 2A region semifinal. The Crusaders handed the Blazers their only loss of the season in the district final, but the rematch was a different story.
Sarasota Christian took leads of 2-0 and 4-2, but Canterbury rallied to tie both times. The Blazers took a 6-4 lead into the sixth.
Canterbury managed cut the lead to a run in the bottom of the sixth but could not rally again.
Patrick Walsh pitched all seven innings for Canterbury (12-15).
"That was really a good high school baseball game," Canterbury coach Dave Smith said. "I'm disappointed we didn't win, but really, this team exceeded expectations this season. We just couldn't get a couple of those key hits."
Photo: Jesuit's Spencer Trayner, left, slides safely into third, beating the tag by Dunedin's Jack Hamrick during the Tigers' 11-1 Class 5A region semifinal victory.
Staff writers Joel Anderson, Bob Putnam and Rodney Page contributed to this report.


text:
The low viral load was a very unusual but not unheard-of finding, meaning we may never know the truth.
For one, she admitted TV documentary crews into her palaces to film her, an unheard-of relaxation of the court protocols.
How can one not pay tribute to the unheard-of tenacity he demonstrated during every stage of this war?
Taymor and his business partner, Ashleigh Parsons, signed the lease and opened Alma an unheard-of two weeks later.
While we were crossing, the German artillery pounded the enemy's position with unheard-of violence.
He spoke as if three thousand dollars was an unheard-of sum, a fortune.
Think, Monsieur Sariette, think of the possible consequences of this unheard-of theft, committed under your eyes.
The priests are credited with unheard-of influence among the poor.
Cheers were raised again and again at the unheard-of wisdom of the King of Troy.
But it comes always as a new thing, an unheard-of thing, a miracle.


text:
February 4, 2013
Electrical hiccup jolted Super Bowl matchup to life
By KEN FIDLIN, QMI Agency
In the Super Bowl era, modern technology has taken sports broadcasting from the horse and buggy days into a future-shock of images that would stun Vince Lombardi if he was alive to see it.
But, for all the computers and cameras, the amazing gadgets and high def that lets you identify a pimple on a fat lineman's butt right through his pants, nothing can still happen without good old-fashioned electricity. Just like the bad old days, television is still held hostage when that squirrel stops running on the treadmill down at ConEd.
Not even the well-oiled Super Bowl production machine was prepared when the lights went out in half the Mercedes Benz Superdome Sunday night, cutting power to the broadcast team of Jim Nantz and Phil Simms.


text:
Pension Alpha
Real Reviews
Real reviews from fellow travellers
These are trusted reviews from guests who have actually stayed here. We hope you find them helpful.
Note: we only give a property a rating once it has received a minimum of 3 reviews.
- Page:1/1
- " Convenient Location ner the Train station "
- 21 Aug 2014 Gunter USA


text:
How do we know Lockmart is the manufacturer?--Toa Quarax (Talk) (Contribs) 01:55, October 29, 2013 (UTC)
- It's in the Tech Manual. I admit my original referencing job doesn't make that very clear though, I'll fiddle with it now.--Leigh Burne (talk) (Contribs) 08:42, October 29, 2013 (UTC)
the Landing ship - In the gallery there is apicture of the landing ship but its labelled as the nostromo. wasnt the landing ship the leviathan or something? -PiLoT-4815 (talk) (Contribs) 01:44, November 5, 2013 (UTC)
- Nope, that is the Nostromo. It's a common misconception that the entire thing seen flying by at the beginning of the film is the Nostromo, but it isn't. The Nostromo is just the little part at the front, towing the refinery, and it is the Nostromo that eventually separates and lands on the moon. The massive refinery itself doesn't have a name, it's just cargo. The Nostromo is like a tractor truck pulling a trailer.
- As for the Leviathan, that was the original name for the Nostromo, before it was changed for the film.--Leigh Burne (talk) (Contribs) 09:05, November 5, 2013 (UTC)
Alien Vault
So I just bought Alien Vault and the schematics are very detailed, but there's one thing that doesn't make much sense. According, to the schematic, the Nostromo had two lifeboats. So maybe the Nostromo just wasn't equipped with it during the events of Alien? Only explanation I could come up with for why the survivors didn't use it (or even mention it) in Alien.--Toa Quarax (Talk) (Contribs) 04:04, January 31, 2014 (UTC)
- Originally the ship was supposed to have two lifeboats, enough for the whole crew to evacuate, but one of them was going to be out of action because it needed repairs. Obviously this is never mentioned in the film, and Ripley implies there's only one shuttle on the Nostromo, so it's debatable whether the two lifeboats thing can be considered canon. I don't know if the shooting script mentions a second lifeboat at all, but it was definitely in earlier drafts. They just changed it for the film.--Leigh Burne (Talk) (Contribs) 08:48, January 31, 2014 (UTC)
About The USCSS Nostromo's Cost To Build
The ship looks so huge that a price of $42 million sounds unrealistic. It would probably cost over $500 billion or ever more seeing how much the space machine in the 1997 movie Contact cost about $300 billion. But then again, seeing how this movie takes place in the future, there could have been some economic change that would make building such huge and advanced spaceships less pricey.
XordaSurvivor (talk) (Contribs) 03:33, September 12, 2014 (UTC)XordaSurvivor
was there something "inside" the Nostromo Rifinery ? Like the sevastopol had many diffrent levels, a Hospital and more, so, what's inside the Nostromo ?--Preceding unsigned comment added by Obi Wan Knoblauch (talk) - Please sign your messages with ~~~~
- Please sign your posts on talk pages.
- The refinery was totally automated, so there weren't any crew areas inside. Maybe a few engineering access spaces, but nothing substantial. The idea was it would process ore automatically while the ship was in transit and the crew was in hypersleep. There'd be no need for anyone to be in there.-- LEIGH BURNE(Talk) 14:40, April 4, 2017 (UTC)


text:
Home » Australia and Oceania » Australia » Cape Tribulation and Daintree Rainforest
This exciting day tour begins when our friendly and experienced driver/guide picks you up from your accommodation. Leaving Cairns and the Northern Beaches, we travel along one of Australia's most spectacular coastal drives to the resort village of Port Douglas. After visiting some of the highlights of Port Douglas, your guide will explain the unique geographic and historic features of the area on route to Mossman Gorge, part of the Daintree Rainforest. At Mossman Gorge, you may like to swim in the cool pristine waters or join your driver for a guided rainforest walk. Back into the comfort of our four-wheel drive vehicle, we head to the Daintree River where morning tea is provided before embarking on a one-hour river cruise.
The Daintree River is home to a diverse ecosystem and the cruise guide will help you spot some of the wildlife including birds, snakes, frogs, flying fox and in the cooler months, crocodiles can be seen lazing on the muddy banks. After the river cruise, we travel up to spectacular Alexander Range Lookout before arriving at our private lunch location at the Daintree Entomological Museum. You will be taken on an informative 20-minute tour around this insect museum and given some fascinating insights into their existence and evolution. After an interesting 20 minutes in the Museum, you will wander over to our private lunch spot where on offer is a splendid barbecue lunch of fresh fish, sumptuous steak and tropical salads and fruits. Enjoy a refreshing swim at our private locations beautiful secluded stream while lunch is cooking or browse a neighboring Butterfly Sanctuary with 100's of our regional species.
After lunch, we travel further north to the isolated Cape Tribulation, where the beach beckons for you to stroll along its' coral sands. There is time to visit the Lookout before departing for the Marrdja Boardwalk for a relaxing and informative one-hour guided walk through the Cape Tribulation National Park. It is by visiting this area that you can appreciate the importance of this rainforest and why it has recently been given World Heritage status. Using your imagination, you could easily picture dinosaurs trudging through this ancient forest. Once again boarding our air-conditioned vehicle to traverse the Alexander Range where you will see the rare and primitive King Ferns growing in abundance.
We then cross the Daintree River by Cable Barge and enjoy a leisurely drive back to Cairns with spectacular views of the Coral Sea. We say farewell to you when we return you to your accommodation doorstep. The tour arrives back in Port Douglas at approximately 5:20 pm and in Cairns at approximately 6:20 pm. Naturalist, David Attenborough, best described his time spent in the Daintree Rainforest as "One of the most magical experiences of my life". We will help ensure that you have the same experience.
Note: Vehicles are comfortable air-conditioned four-wheel drives, carrying a maximum of 13 and 16 passengers.
About This Supplier
Also see tour packages in:
Australia and Oceania Australia Nature & Wildlife Rainforest
Email it to a friend:
Click here to email this vacation to a friend


text:
Position: Pitcher
DOB: September 15, 1984
Height: 7'1''
Weight: 225
Bats: Right
Throws: Right
Loek Van Mil has been playing the game of baseball since he was eight years old, although one look at him and you would swear that he is a member of the National Basketball Association. Standing 7'1'' tall, the young right-hander is the tallest player in professional baseball, and he has definitely garnered enough attention this past year just because of that. However, he is also developing into quite a pitcher, and if he can continue to progress, then he will be the tallest player to ever play in the Major Leagues.
The Twins began scouting Van Mil three years ago, and he had also been drawing some interest from the Seattle Mariners. Van Mil had his heart set on being a Twins, and even told the Star-Tribune that it did not matter how much money Seattle offered. Now that he is with the Twins, Van Mil has been called a "project", but he is definitely a prospect with tremendous upside.
A Darren Daulton fan growing up, Van Mil was switched to pitcher due to his size, and the rest is history.
During the 2006 season, Van Mil had a successful inaugural year of professional baseball, as he was worked as both a reliever and a starter. The Netherlands-native appeared in ten games for the Gulf Coast League Twins, making eight starts, and had a respectable 3.30 earned run average. He pitched far better than anyone could have expected.
In 2007, Van Mil was a member of the Dutch National Team in the World Baseball Cup, and pitched exceptionally well. He posted a 0.71 earned run average in his time with the team, notching two saves. It would set the stage for him to be promoted to Elizabethton.
For the E-Town Twins, Van Mil helped the team to the Appalachian League Championship, as he pitched much better in his second season with the Twins. Van Mil posted a 2.63 earned run average, notching a 2-2 record. Van Mil struck out nearly a batter per inning, and really showed growth from year one.
This past season, Van Mil got his first taste of full-season baseball, appearing in 28 games for the Beloit Snappers. The young right-hander fared well in a relief role for the team, posting a 3.22 earned run average. Once again, Van Mil struck out nearly a batter per inning, and he held the opposition to a .222 batting average.
Repertoire: Fastball, Slider, Changeup
Fastball: When the Twins first got a look at Van Mil, the lanky right-hander's fastball sat in the high-80s. Since then, Van Mil has made some huge strides, using his frame to his advantage. After hitting the low-90s last season, Van Mil reached the mid-90s this past season, and is starting to show much better accuracy with his fastball.
Other Pitches: Van Mil has two other pitches that he is beginning to be able to throw for strikes. The right-hander's slider is developing quite nicely, and he has also been honing his skills with his changeup. He has been able to spot his pitches much better as of late, though a sore elbow ended his 2007 season. The slider is definitely his number two pitch, and he has begun showing much more consistency with it.
Pitching: The main thing for Van Mil has been consistency. Since he came to the Twins, they have been hoping that he could use his big frame to dominate the opposition, which he is starting to do. His earned run average has lowered from year one, and he is striking people out at a much better pace. His consistency is getting better, and so has his confidence, as he now wants to be seen as a great pitcher, not just a tall pitcher. Once his delivery gets more fluid, he should be a top-10 pitching prospect in the Twins organization.
Projection. Van Mil was used exclusively out of the bullpen in 2007, after spending time between the rotation and bullpen in 2006. In 2008, the tall righty was used only in a relief role, and that is where he projects in the future. It would be something for the Twins to trot out a 7-foot-1 inch righty to nail down a big out late in the game.
ETA 2011. The Twins have been using kid gloves with Van Mil since he came into the organization, and I believe that he will be babied until he shows more consistency. Van Mil will likely be with Fort Myers next season, as the Twins have taken a level-by-level approach with him. Still, he is no longer just a tall guy in the organization. He is a legitimate prospect now, and one that continues to impress.


text:
The Randa Meetings as the annual KDE Tech Summit are back. This year a bit earlier to not clash with QtCon and for some other reasons. So if you want to join us from Sunday, the 12th to Sunday the 19th of June 2016 in the middle of Alps don't hesitate, get in contact with us and register yourself. The registration will close March, 16th so we can start to work on a budget and continue with the organization.
The main topic of the Randa Meetings 2016 (RM2016) will be multi-platform end-user application development. This includes stuff like improving KDE Frameworks 5 (KF5) on other platforms like Microsoft Windows, Android or Apple's MacOSX, presenting and discussing how software distribution works on other systems than GNU/Linux (Windows installers, app stores and application bundles) and learning from the experience projects like Krita, digiKam, Rkward, Kdenlive & Co collected. We'd like to bring this information to more KDE Applications and work on this during a full week.
Are you interested in C++ programming on a certain operating system, do you know the internal functions of the underlying system or are you well-known for porting Qt applications to other operating systems than GNU/Linux then we need you. Or do you just want to port your KDE application to another OS then please add yourself too.
Do you have knowledge about the software distribution channels and mechanisms on the popular systems and have experience in creating installation software for MS Windows, application bundles for MacOSX or repositories for F-Droid and want to share this knowledge and help a great and welcoming Free Software community to bring their software to this systems? Then please get in contact and come to Randa, Switzerland in June 2016.
If there are any questions, don't hesitate to get in contact (email, comments section below or IRC: freenode.net in #randa). And if you know somebody else that would fit please forward this information and spread the word about it. See you soon in Randa…


text:
Tragic news for benched baller Lamar Odom. The 15-year-old boy who was hit by Lamar's chauffeur-driven town car on Friday in New York has died in a hospital, TMZ reports.
Odom was in town to attend a funeral for his cousin and had hired a car service to drive him around. On Friday, the car—with Odom in it—was involved in an accident with a motorcycle, and the unnamed 15-year-old was caught in the cross hairs. He was rushed to the hospital where it was found out that the boy had sustained major head injuries. Doctors performed emergency surgery to try to save his life, but were unsuccessful.
Odom is said to be "devastated" by the tragedy.


text:
Coromandel's year ahead is open for submissions
Coromandel's year ahead is open for submissions
Our Draft 2014/15 Annual Plan is now out and open for submissions.
We think the future is looking good for the Coromandel but we still have to work hard to get there.
Thames-Coromandel District Council Chief Executive David Hammond says economic development is not just about property development; it's about local employment, people coming into the Coromandel and getting more ratepayers moving here to live and build our great communities.
"As well as investing in our big priorities - the Coromandel Great Walk, Coromandel Harbour facilities, and, the Hauraki Rail Trail - we will be looking to implement our broader Economic Development Strategy adopted by Council in 2013," Mr Hammond says.
"But we're also asking to change the way we raise money for economic development. A notable amount of that is currently being paid by about 970 commercial properties. We're proposing to cap that amount on those commercial rates, because if you put that economic development increase on just those 970 commercial properties, we'll drive them out of business. Therefore, in short, we're asking all ratepayers to pay a greater contribution for this activity. In my view, everyone in the community benefits from economic and population growth - our schools, shops, sport clubs and our hospital."
As well as putting out the proposal, Mr Hammond has tasked Council staff with further options to reduce the 2014/15 operational budget from what is in the draft Annual Plan without cutting services.
"The great thing about local government is that people still have a right and an avenue to question their rates. Councils are not like some faceless utilities who don't hear the cost-of-living concerns of ordinary New Zealanders. You can make submissions on rates - and speak to that submission," he says."
So take a look at the Draft 2014/15 Annual Plan. Start with what you're interested in, perhaps, and the things you feel need to be done in your community.
Ask us about anything you don't understand.
And remember that if you do see the project you've wanted in the draft plan and you don't submit with your support, it might get rejected if others submit against it. Give your favourite ideas the support they need by making a submission for them.
Please read the draft plan. Then make a submission. You'll find all the details here:www.tcdc.govt.nz/ap
P.S. You can also pick up printed versions at Council offices and District Libraries.


text:
- Introduction
- WebConsole Plugin
- WebTail
- Initial Configuration
- User Configuration - OSGi Based
- Logback Integration
- TurboFilters as OSGi Services
- Filters as OSGi services
- Appenders as OSGi services
- Logback Config Fragment Support
- External Config File
- Java Util Logging (JUL) Integration
- Configuring OSGi appenders in the Logback Config
- Using Slf4j API 1.7
- Log Tracer
- Slf4j MDC
- Logback Groovy Fragment
Logging in Sling is supported by the
org.apache.sling.commons.log bundle, which is one of the first bundles installed
and started by the Sling Launcher. This bundle along with other bundles manages the Sling Logging and provides the
following features:
- Implements the OSGi Log Service Specification and registers the
- Exports three commonly used logging APIs:
- Simple Logging Facade for Java (SLF4J)
- Apache Commons Logging
- log4j
- java.util.logging
- Configures logging through Logback which is integrated with the OSGi environment
- Allows logging to be configured both via editing Logback xml or via OSGi Configurations
v5.0.0 release¶
With Sling Log 5.0.0. release the webconsole support has been moved to a different bundle named Sling Commons Log WebConsole (org.apache.sling.commons.log.webconsole:1.0.0)
Also with this release Logback 1.1.7 version is embedded and thus it requires slf4j-api:1.7.15. See SLING-6144 for details
WebConsole Plugin¶
The Web Console Plugin supports the following features:
- Display the list of loggers which have levels or appenders configured.
- List the file appenders with the location of current active log files.
- Show the contents of LogBack config files.
- Show the contents of various Logback config fragments.
- Show Logback Status logs.
- Inline edit the Logger setting
- Configure Logger with content assist for logger names
- Provides links to log file content allows log file content to be viewed from Web UI
The Web Console Plugin also supports tailing of the current active log files. It generates link to all active log files which can be used to see there content from within the browser. The url used is like
It supports following parameters
name- Appender name like /logs/error.log
tail- Number of lines to include in dump. -1 to include whole file
grep- Filter the log lines based on
grepvalue which can be
- Simple string phrase - In this case search is done in case insensitive way via String.contains
- regex - In this case the search would be done via regex pattern matching
Initial Configuration¶
org.apache.sling.commons.log bundle gets its initial configuration from the following
BundleContext properties:
|Sets the initial logging level of the root logger. This may be any of the defined logging levels
ERROR and
|Sets the log file to which log messages are written. If this property is empty or missing, log messages are written to
|The number of rotated files to keep.
|Defines how the log file is rotated (by schedule or by size) and when to rotate. See the section Log File Rotation below for full details on log file rotation.
|{0,date,dd.MM.yyyy HH:mm:ss.SSS} *{4}* [{2}]() {3} {5}
MessageFormat pattern to use for formatting log messages with the root logger.
|Enables the
java.util.logging support.
|Path for the Logback config file which would be used to configure logging. If the path is not absolute then it would be resolved against Sling Home
|Boolean property to control packaging data support of Logback. See Packaging Data section of Logback for more details
|Number of lines from each log files to include while generating the dump in 'txt' mode. If set to -1 then whole file would be included
|Maximum number of old rolled over files for each active file to be included while generating the dump as part of Status zip support
|Sling Home
|The directory, which is used to resolve relative path names against. If not specified it would map to sling.home. Since 4.0.2
User Configuration - OSGi Based¶
User Configuration after initial configuration is provided by the Configuration Admin Service. To this avail two
org.osgi.services.cm.ManagedServiceFactory services are registered under the PIDs
org.apache.sling.commons.log.LogManager.factory.config to receive configurations.
Logger Configuration¶
Loggers (or Categories) can be configured to log to specific files at specific levels using configurable patterns.
To this avail factory configuration instances with factory PID
may be created and configured with the Configuration Admin Service.
The following properties may be set:
|Sets the logging level of the loggers. This may be any of the defined logging levels
ERROR and
|Sets the log file to which log messages are written. If this property is empty or missing, log messages are written to
System.out. This property should refer to the file name of a configured Log Writer (see below). If no Log Writer is configured with the same file name an implicit Log Writer configuration with default configuration is created.
|{0,date,dd.MM.yyyy HH:mm:ss.SSS} *{4}* [{2}]() {3} {5}
java.util.MessageFormat pattern to use for formatting log messages with the root logger. This is a
java.util.MessageFormat pattern supporting up to six arguments: {0} The timestamp of type
java.util.Date, {1} the log marker, {2} the name of the current thread, {3} the name of the logger, {4} the log level and {5} the actual log message. If the log call includes a Throwable, the stacktrace is just appended to the message regardless of the pattern.
|A list of logger names to which this configuration applies.
|If set to false then logs from these loggers would not be sent to any appender attached higher in the hierarchy
Note that multiple Logger Configurations may refer to the same Log Writer Configuration. If no Log Writer Configuration exists whose file name matches the file name set on the Logger Configuration an implicit Log Writer Configuration with default setup (daily log rotation) is internally created. While the log level configuration is case insensitive, it is suggested to always use upper case letters.
Log Writer Configuration¶
Log Writer Configuration is used to setup file output and log file rotation characteristics for log writers used by the Loggers.
The following properties may be set:
|Sets the log file to which log messages are written. If this property is empty or missing, log messages are written to
|The number of rotated files to keep.
|Defines how the log file is rotated (by schedule or by size) and when to rotate. See the section Log File Rotation below for full details on log file rotation.
See the section Log File Rotation below for full details on the
org.apache.sling.commons.log.file.size and
org.apache.sling.commons.log.file.number properties.
Log File Rotation¶
Log files can grow rather quickly and fill up available disk space. To cope with this growth log files may be rotated in
two ways: At specific times or when the log file reaches a configurable size. The first method is called Scheduled Rotation
and is used by specifying a
SimpleDateFormat pattern as the log file "size". The second method is called Size Rotation
and is used by setting a maximum file size as the log file size.
As of version 2.0.6 of the Sling Commons Log bundle, the default value for log file scheduling is
causing daily log rotation. In previous version, log rotation defaults to a 10MB file size limit.
Scheduled Rotation¶
The rolling schedule is specified by setting the
org.apache.sling.commons.log.file.size property to a
java.text.SimpleDateFormat pattern. Literal text (such as a leading dot) to be included must be enclosed within a
pair of single quotes. A formatted version of the date pattern is used as the suffix for the rolled file name. Internally
the Log bundle configures a
TimeBasedRollingPolicy for the appender. Refer to TimeBasedRollingPolicy for
more details around the pattern format
For example, if the log file is configured as
/foo/bar.log and the pattern set to
'.'yyyy-MM-dd, on
2001-02-16 at midnight, the logging file
/foo/bar.log will be renamed to
/foo/bar.log.2001-02-16 and logging for
2001-02-17 will continue in a new
/foo/bar.log file until it rolls over the next day.
It is possible to specify monthly, weekly, half-daily, daily, hourly, or minutely rollover schedules.
|Rollover schedule
|Rollover at the beginning of each month
|At midnight of May 31st, 2002
/foo/bar.log will be copied to
/foo/bar.log.2002-05. Logging for the month of June will be output to
/foo/bar.log until it is also rolled over the next month.
|Rollover at the first day of each week. The first day of the week depends on the locale.
|Assuming the first day of the week is Sunday, on Saturday midnight, June 9th 2002, the file
/foo/bar.log will be copied to
/foo/bar.log.2002-23. Logging for the 24th week of 2002 will be output to
/foo/bar.log until it is rolled over the next week.
|Rollover at midnight each day.
|At midnight, on March 8th, 2002,
/foo/bar.log will be copied to
/foo/bar.log.2002-03-08. Logging for the 9th day of March will be output to
/foo/bar.log until it is rolled over the next day.
|Rollover at midnight and midday of each day.
|at noon, on March 9th, 2002,
/foo/bar.log will be copied to
/foo/bar.log.2002-03-09-AM. Logging for the afternoon of the 9th will be output to
/foo/bar.log until it is rolled over at midnight.
|Rollover at the top of every hour.
|At approximately 11:00.000 o'clock on March 9th, 2002,
/foo/bar.log will be copied to
/foo/bar.log.2002-03-09-10. Logging for the 11th hour of the 9th of March will be output to
/foo/bar.log until it is rolled over at the beginning of the next hour.
|Rollover at the beginning of every minute.
|At approximately 11:23,000, on March 9th, 2001,
/foo/bar.log will be copied to
/foo/bar.log.2001-03-09-10-22. Logging for the minute of 11:23 (9th of March) will be output to
/foo/bar.log until it is rolled over the next minute.
Do not use the colon ":" character in anywhere in the pattern option. The text before the colon is interpreted as the protocol specification of a URL which is probably not what you want.
Note that Scheduled Rotation ignores the
org.apache.sling.commons.log.file.number property since the old log files are
not numbered but "dated".
Size Rotation¶
Log file rotation by size is specified by setting the
org.apache.sling.commons.log.file.size property to a plain number
or a number plus a size multiplier. The size multiplier may be any of
G, or
GB where the case
is ignored and the meaning is probably obvious.
When using Size Rotation, the
org.apache.sling.commons.log.file.number defines the number of old log file generations
to keep. For example to keep 5 old log files indexed by 0 through 4, set the
5 (which happens to be the default).
Logback Integration¶
Logback integration provides following features
- LogBack configuration can be provided via Logback config xml
- Supports Appenders registered as OSGi Services
- Supports Filters and TurboFilters registered as OSGi Services
- Support providing Logback configuration as fragments through OSGi Service Registry
- Support for referring to Appenders registered as OSGi services from with Logback config
- Exposes Logback runtime state through the Felix WebConsole Plugin
The following sections provide more details.
TurboFilters as OSGi Services¶
Logback TurboFilters operate globally and are invoked for every Logback call. To register an OSGi
just to register an service that implements the
ch.qos.logback.classic.turbo.TurboFilter interface.
import import ch.qos.logback.classic.turbo.MatchingFilter; SimpleTurboFilter stf = new SimpleTurboFilter(); ServiceRegistration sr = bundleContext.registerService(TurboFilter.class.getName(), stf, null); private static class SimpleTurboFilter extends MatchingFilter { @Override public FilterReply decide(Marker marker, Logger logger, Level level, String format, Object[] params, Throwable t) { if(logger.getName().equals("turbofilter.foo.bar")){ return FilterReply.DENY; } return FilterReply.NEUTRAL; } }
As these filters are invoked for every call they must execute quickly.
Filters as OSGi services¶
Logback Filters are attached to appenders and are used to determine if any LoggingEvent needs to
be passed to the appender. When registering a filter the bundle needs to configure a service property
appenders which refers to list of appender names to which the Filter must be attached
import ch.qos.logback.core.filter.Filter; SimpleFilter stf = new SimpleFilter(); Dictionary<String, Object> props = new Hashtable<String, Object>(); props.put("appenders", "TestAppender"); ServiceRegistration sr = bundleContext.registerService(Filter.class.getName(), stf, props); private static class SimpleFilter extends Filter<ILoggingEvent> { @Override public FilterReply decide(ILoggingEvent event) { if(event.getLoggerName().equals("filter.foo.bar")){ return FilterReply.DENY; } return FilterReply.NEUTRAL; } }
If the
appenders value is set to
* then the filter would be registered with all the appenders (
Since 4.0.4)
Appenders as OSGi services¶
Logback Appenders handle the logging events produced by Logback. To register an OSGi
just register a service that implements the
ch.qos.logback.core.Appender interface. Such a service must
have a
loggers service property, which refers to list of logger names to which the Appender must be attached.
Dictionary<String,Object> props = new Hashtable<String, Object>(); String[] loggers = { "foo.bar:DEBUG", "foo.bar.zoo:INFO", }; props.put("loggers",loggers); sr = bundleContext.registerService(Appender.class.getName(),this,props);
Logback Config Fragment Support¶
Logback supports including parts of a configuration file from another file (See File Inclusion). This module extends that support by allowing other bundles to provide config fragments. There are two ways to achieve that, described below.
Logback config fragments as String objects¶
If you have the config as string then you can register that String instance as a service with property
set to true. The Sling Logback Extension monitors such objects and passes them to logback.
Properties props = new Properties(); props.setProperty("logbackConfig","true"); String config = "<included>\n" + " <appender name=\"FOOFILE\" class=\"ch.qos.logback.core.FileAppender\">\n" + " <file>${sling.home}/logs/foo.log</file>\n" + " <encoder>\n" + " <pattern>%d %-5level %logger{35} - %msg %n</pattern>\n" + " </encoder>\n" + " </appender>\n" + "\n" + " <logger name=\"foo.bar.include\" level=\"INFO\">\n" + " <appender-ref ref=\"FOOFILE\" />\n" + " </logger>\n" + "\n" + "</included>"; registration = context.registerService(String.class.getName(),config,props);
If the config needs to be updated just re-register the service so that changes are picked up.
Logback config fragments as ConfigProvider instances¶
Another way to provide config fragments is with services that implement the
org.apache.sling.commons.log.logback.ConfigProvider interface.
@Component @Service public class ConfigProviderExample implements ConfigProvider { public InputSource getConfigSource() { return new InputSource(getClass().getClassLoader().getResourceAsStream("foo-config.xml")); } }
If the config changes then sending an OSGi event with the
org/apache/sling/commons/log/RESET topic
resets the Logback runtime.
eventAdmin.sendEvent(new Event("org/apache/sling/commons/log/RESET",new Properties()));
External Config File¶
Logback can be configured with an external file. The file name can be specified through
- OSGi config - Look for a config with name
Apache Sling Logging Configurationand specify the config file path.
- OSGi Framework Properties - Logback support also looks for a file named according to the OSGi framwork
If you are providing an external config file then to support OSGi integration you need to add following action entry:
<newRule pattern="*/configuration/osgi" actionClass="org.apache.sling.commons.log.logback.OsgiAction"/> <newRule pattern="*/configuration/appender-ref-osgi" actionClass="org.apache.sling.commons.log.logback.OsgiAppenderRefAction"/> <osgi/>
osgi element enables the OSGi integration support
Java Util Logging (JUL) Integration¶
The bundle also support SLF4JBridgeHandler. The two steps listed below enable the JUL integration. This allows for routing logging messages from JUL to the Logbback appenders.
- Set the
org.apache.sling.commons.log.julenabledframework property to true.
org.apache.sling.commons.log.julenabled is found to be true then LevelChangePropagator would be
registered automatically with Logback
Configuring OSGi appenders in the Logback Config¶
So far Sling used to configure the appenders based on OSGi config. This provides a very limited set of configuration options. To make use of other Logback features you can override the OSGi config from within the Logback config file. OSGi config based appenders are named based on the file name.
For example, for the following OSGi config
org.apache.sling.commons.log.file="logs/error.log" org.apache.sling.commons.log.level="INFO" org.apache.sling.commons.log.file.size="'.'yyyy-MM-dd" org.apache.sling.commons.log.file.number=I"7" org.apache.sling.commons.log.pattern="{0,date,dd.MM.yyyy HH:mm:ss.SSS} *{4}* [{2}] {3} {5}"
The Logback appender would be named
logs/error.log. To extend/override the config in a Logback config
create an appender with the name
<appender name="/logs/error.log" class="ch.qos.logback.core.FileAppender"> <file>${sling.home}/logs/error.log</file> <encoder> <pattern>%d %-5level %X{sling.userId:-NA} [%thread] %logger{30} %marker- %msg %n</pattern> <immediateFlush>true</immediateFlush> </encoder> </appender>
In this case the logging module creates an appender based on the Logback config instead of the OSGi config. This can be used to move the application from OSGi based configs to Logback based configs.
Using Slf4j API 1.7¶
With Slf4j API 1.7 onwards its possible to use logger methods with varargs i.e. log n arguments without
constructing an object array e.g.
log.info("This is a test {} , {}, {}, {}",1,2,3,4). Without var args
you need to construct an object array
log.info("This is a test {} , {}, {}, {}",new Object[] {1,2,3,4}).
To make use of this API and still be able to use your bundle on Sling systems which package older version
of the API jar, follow the below steps. (See SLING-3243) for more details.
Update the api version in the pom:
<dependencies> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.7.5</version> <scope>provided</scope> </dependency> ... </dependency>
Add an
Import-Packageinstruction with a custom version range:
<build> <plugins> <plugin> <groupId>org.apache.felix</groupId> <artifactId>maven-bundle-plugin</artifactId> <extensions>true</extensions> <configuration> <instructions> ... <Import-Package> org.slf4j;version="[1.5,2)", * </Import-Package> </instructions> </configuration> </plugin> ... </plugins> </build>
The Slf4j API bundle 1.7.x is binary compatible with 1.6.x.
This setup allows your bundles to make use of the var args feature while making logging calls, but the bundles can still be deployed on older systems which provide only the 1.6.4 version of the slf4j api.
Log Tracer¶
Log Tracer provides support for enabling the logs for specific category at specific level and only for specific request. It provides a very fine level of control via config provided as part of HTTP request around how the logging should be performed for given category.
Refer to Log Tracer Doc for more details
Slf4j MDC¶
Sling MDC Inserting Filter exposes various request details as part of MDC.
Currently it exposes following variables:
req.remoteHost- Request remote host
req.userAgent- User Agent Header
req.requestURI- Request URI
req.queryString- Query String from request
sling.userId- UserID associated with the request. Obtained from ResourceResolver
jcr.sessionId- Session ID of the JCR Session associated with current request.
The filter also allow configuration to extract data from request cookie, header and parameters. Look for configuration with name 'Apache Sling Logging MDC Inserting Filter' for details on specifying header, cookie, param names.
Including MDC in Log Message¶
To include the MDC value in log message you MUST use the Logback pattern based on Logback and not the old MessageFormat based pattern.
%d{dd.MM.yyyy HH:mm:ss.SSS} *%p* [%X{req.remoteHost}] [%t] %c %msg%n
Download the bundle from here or use following Maven dependency
<dependency> <groupId>org.apache.sling</groupId> <artifactId>org.apache.sling.extensions.slf4j.mdc</artifactId> <version>1.0.0</version> </dependency>
Logback Groovy Fragment¶
This fragment is required to make use of Groovy based event evaluation support provided by Logback. This enables programatic filtering of the log messages and is useful to get desired logs without flooding the system. For example Oak logs the JCR operations being performed via a particular session. if this lo is enabled it would flood the log with messages from all the active session. However if you need logging only from session created in a particular thread then that can be done in following way
<?xml version="1.0" encoding="UTF-8"?> <configuration scan="true" scanPeriod="1 second"> <jmxConfigurator/> <newRule pattern="*/configuration/osgi" actionClass="org.apache.sling.commons.log.logback.OsgiAction"/> <newRule pattern="*/configuration/appender-ref-osgi" actionClass="org.apache.sling.commons.log.logback.OsgiAppenderRefAction"/> <osgi/> <appender name="OAK" class="ch.qos.logback.core.FileAppender"> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator class="ch.qos.logback.classic.boolex.GEventEvaluator"> <expression><![CDATA[ return e.getThreadName().contains("JobHandler"); ]]></expression> </evaluator> <OnMismatch>DENY</OnMismatch> <OnMatch>ACCEPT</OnMatch> </filter> <file>${sling.home}/logs/oak.log</file> <encoder> <pattern>%d %-5level [%thread] %marker- %msg %n</pattern> <immediateFlush>true</immediateFlush> </encoder> </appender> <logger name="org.apache.jackrabbit.oak.jcr.operations" level="DEBUG" additivity="false"> <appender-ref ref="OAK"/> </logger> </configuration>
Logback exposes a variable
e which is of type ILoggingEvent. It provides access to current logging
event. Above logback config would route all log messages from
category to
${sling.home}/logs/oak.log. Further only those log messages would be logged
where the
threadName contains
JobHandler. Depending on the requirement the expression can
be customised.
Currently the bundle is not released and has to be build from here
<dependency> <groupId>org.apache.sling</groupId> <artifactId>org.apache.sling.extensions.logback-groovy-fragment</artifactId> <version>1.0.0-SNAPSHOT</version> </dependency>
Q. Can Sling Commons Log bundle be used in non Sling environments¶
This bundle does not depend on any other Sling bundle and can be easily used in any OSGi framework. To get complete log support working you need to deploy following bundles
- Slf4j-Api - org.slf4j:slf4j-api
- Jcl over Slf4j - org.slf4j:jcl-over-slf4j
- Log4j over Slf4j - org.slf4j:log4j-over-slf4j
- Sling Log Service - org.apache.sling:org.apache.sling.commons.logservice:1.0.2
- Sling Commons Log - org.apache.sling:org.apache.sling.commons.log:4.0.0 or above
- Sling Log WebConsole - org.apache.sling.commons.log.webconsole:1.0.0 or above
Q. How to start Sling with an external logback.xml file¶
You need to specify the location of logback.xml via
java -jar org.apache.sling.launchpad-XXX-standalone.jar -Dorg.apache.sling.commons.log.configurationFile=/path/to/logback


text:
Terror trial told of Sydney suicide attack plot
Page Tools
Mallah ... accused of bomb plot.
Photo: Rick Stevens
A young terror suspect planned a suicide attack on a building accommodating intelligence officers and foreign affairs personnel after he was refused a passport, a Sydney court was told today.
The NSW District Court today began hearing the trial of Zeky "Zak" Mallah, 21, who has pleaded not guilty to charges under Australia's counter-terror laws.
He is accused of plotting to carry out a suicide attack on the Sydney offices of the Department of Foreign Affairs and Trade or the Australian Security and Intelligence Organisation, in late 2003.
The Crown claims he planned to kill ASIO or DFAT officers in the attack.
He also pleaded not guilty to offering to sell a video tape, typed statement and photograph of himself to an undercover police officer who he thought was a journalist, between November 2003 and December 2003.
Crown Prosecutor Desmond Fagan, SC, today told the court the tape and statement related to the planned attacks, and Mallah also told the undercover officer he wanted to kill commonwealth officers.
Mr Fagan said Mallah planned the attack after DFAT refused him a passport in mid-2002.
"As a result of that refusal he developed a hostility to that department and ASIO", Fagan said.
The trial continues.
Get the SMH delivered for as little as $3 a week - SAVE 21%


text:
by Staff Writers
Kabul (AFP) Nov 23, 2012
A network of informers, exploitation of popular dissent and the ability to strike at vulnerable moments helped hasten the end of France's combat mission in Afghanistan, according to a Taliban commander.
French troops rolled out of Kapisa province on Tuesday, ending one of the largest NATO combat missions in Afghanistan two years early, 10 months to the day since Afghan soldier Abdul Sabor shot dead five French colleagues.
The Taliban regularly take credit for "green-on-blue" attacks, but while Sabor's links to insurgents have never been confirmed, his actions left a profound impact on French troops on the ground and political will at home.
France entered Kapisa province and its neighbouring Surobi district in Afghanistan's northeast in 2007. Home to mafia, Taliban, and Hezb-e-Islami fighters with a toxic hatred of "invaders", they were in for a rough welcome.
"(The French) were not aware of the ground conditions. When there is a direct fight, we know exactly how to trap our enemies in the mountains, just like we did with the Soviets," says Bilal, a Taliban commander in Kapisa.
In August 2008, shortly after arriving in Surobi, 10 soldiers were killed in an ambush. At the time, it was the deadliest ground attack suffered by NATO in Afghanistan.
Seen as working for the Americans, whose invasion brought down the 1996-2001 Taliban regime, the French quickly lost any goodwill they once enjoyed among mujahedeen for charity work in the 1980s.
On top of the homemade bombs, ambushes and suicide attacks, the rebels claim to control a large network of informers, including Afghan soldiers working with NATO who support the Islamist uprising in secret.
"As soon as the French were moving in Kapisa or Surobi, we were aware of it," said Bilal, who claims to have up to 200 men at his disposal.
A Taliban exile speaking to AFP in Pakistan confirmed the same thing.
"We have informers inside bases everywhere," Bilal added. If they wanted a suicide bomber they called a specific number to inform central command.
The bomber would then arrive.
"Nobody knows where he comes from. It's our master weapon," said Bilal.
The rate of French fatalities quickly escalated. There were three in 2007, 11 in 2008 and 2009, 16 in 2010, 26 in 2011 and 10 so far in 2012, the majority in Kapisa.
The insurgents, whom the Afghan army estimates in Kapisa to number 250 in winter and 500 in summer, were on paper overwhelmed by the 2,500 French soldiers.
But in Paris, politicians worried about the bloodshed and started to discuss early retreat. Opponents thought it too risky to alienate their allies.
Others argued it made perfect financial sense against a backdrop of the euro crisis (the Afghan mission cost 500 million euros, or $642 million) in 2012.
After a suicide attack killed five soldiers on July 13, 2011, the French were told to stop going deep into the countryside. By autumn, Bilal says they "stayed in their bases and rarely went to towns".
Then Afghan police and soldiers stepped up attacks on NATO colleagues, although it remains unclear how many were directly dispatched by the Taliban.
"We sometimes identify soldiers who could potentially carry such attacks. We contact them through their family and convince them," said Bilal.
Shortly after Sabor shot five French colleagues out jogging on a military base, then-president Nicolas Sarkozy announced that French soldiers would withdraw in 2013, a year earlier than the deadline set by NATO.
In May, his successor Francois Hollande brought the date forward to 2012.
The French army says it had "no suspicion" of an insurgent infiltration.
But some facts remain troubling.
Such as the suicide bomber who killed four French soldiers on June 9, apparently lying in wait and blowing himself up as soon as the French soldiers got out of a vehicle only moments after arriving in a village.
The French are committed to development projects in Kapisa until 2016, and apparently the rebels do not rule out accepting them back.
"We're expecting France to contribute to peace and stability in the region, but with no strings attached. The end of combat doesn't meant we are going to cut all links," said Hezb-e-Islami spokesman Ghairat Baheer.
Related Links
News From Across The Stans
|The content herein, unless otherwise known to be public domain, are Copyright 1995-2014 - Space Media Network. AFP, UPI and IANS news wire stories are copyright Agence France-Presse, United Press International and Indo-Asia News Service. ESA Portal Reports are copyright European Space Agency. All NASA sourced material is public domain. Additional copyrights may apply in whole or part to other bona fide parties. Advertising does not imply endorsement,agreement or approval of any opinions, statements or information provided by Space Media Network on any Web page published or hosted by Space Media Network. Privacy Statement