Comments (0) 
此劇追了近1個月，昨晚終於觀看完畢首3季和最後的那集Downton Abbey 2012 Christmas Special。想到又要等一年才有完整的第4季，真有點欲罷不能的感覺。
Downton Abbey是近年少見的出色British Drama，那個年代的人和事物都很Decent，就如最近看過的另一傑作Brideshead Revisited般精彩。
很喜歡這些英國的古堡大宅和它們背後的文化背景故事，有機會一定會去Highclere Castle與Castle Howard看看。
Highclere Castle
Castle Howard
Honda NSX Type R 92 Ltd Ed Formula Red, Championship White or Pearl Yellow
Jaguar Long Nose D-Type 1st LeMans 55 Ltd Ed Hawthorn/Bueb dark green w/white nose stripe #6
Jaguar E-Type Series II 4.2 Roadster Red w/Metal Wire-spoke Wheels
Ford GT Ltd Ed Black w/white stripes, White w/black or Titanium w/silver
Koenigsegg Agera 13 Red, Silver Gray, or White
McLaren MP4-12C Ltd Ed in Orange, Red or Silver
Porsche 928 S 83 Ltd Ed Guards Red or Silver
附近商場今天又搞Top Gear年度最佳車展，也第二次見到了McLaren MP4-12C。
說實話，比起前輩F1 GTR的風范，它真的沒什么吸引力。
驚喜的反而是Benz SL Class，朦朧之間還以為是超跑SLS。
This is probably the very first song introduced by my mum when I was very young.
How Much is That Doggie in The Window
When I am older now, I like the following two:
I Went To Your Wedding
Tenessee waltz, but somehow I like Norah Jones’s version more.
It’s a very common scenario that a server/PC maintained by careless keeper got hacked, which often leads to high CPU usage due to Trojan process running in background.
The followings two are the most useful tools to quickly determine which are the bad nuts.
netstat -nop tcp
- This is very useful to find out if a Trojan service has opened an incoming port, often the status shows “ESTABLISHED”
- netstat can be also used to find out the DDOS IP as those status often ends with “LAST_ACK”
- From the output PID, then you can determine which process from the task manager, but what if it’s a svhost.exe? Problem is you still can’t tell exactly which service as there are several svhost.exe running most of the time, so keep reading.
tasklist /svc |find “Process_ID”
Bingo! This cmd does exactly the trick to find out which is the bad nuts, Process_ID or PID is the one you got in netstat.
Is that so simple? I am afraid not, I’ve seen recently Trojan/DDOS tools have becoming more sophisticated and difficult to catch as they embedded themselves as web scripts utilizing UDP ports as the protocol, either acts as a bot waiting to be activated via URL strings and then send UDP DDOS to the target IP (ie attack others) or exhausts the entire server CPU by issuing UDP commands to fill up Events Logger (ie, attacked the server itself).
What you will find is w3wp.exe (or IIS Service) is using a lot of CPU as well as System (which is the disk activity) being very busy, so you got to use other methods to track down those bad scripts.
Finally, a single svchost.exe can contain many individual services, so the only way to find out which service is responsible is to configure them to run in its separate svchost.
For example, lets start with wuauserv (Windows Update Service) which is often the cause of high CPU, open command prompt and run the following commands:
net stop wuauserv
sc config wuauserv type= own
net start wuauserv
This will isolate wuauserv in its own svchost and then you can check the effect on CPU and identify the PID with tasklist /svc, you are already familiar with the process.
Onion Soup with Parmesan Cheese
Spanish Iberian Pork with Fries from McDonald 
Red Wine from Bordeaux
French Lemon Tart
今天午飯出去的時候在停車場突然發現鄰居入手了台漂亮的紅色Alfa Romeo 1600 Duetto Spider小跑車，相比之下，AA的那台紅色明顯偏橙色，貨不對辦，幸虧沒買。
