幻想仿佛只属于年轻了,想到这里,我突然想问自己,我还是年轻人吗,或许10年前我会不加思索的说YES,但是现在我连NO都不敢说了。
是生活禁锢思想还是思想禁锢了生活,说YES说NO在不同的时代却都变得不能一概而论,但是人生就好像箭在弦上,总有发射的那一刻,没有做好准备也由不得你迟疑片刻。
不能说NO,更不能说YES,我多渴望找回遗失的幻想,说一句“You know, It doesn't matter.” 。因为真正重要的是你提醒了我,该去找回那些遗失dē幻想的时候到了。
Wednesday, April 21, 2010
为什么叫oracle1.com
凡是名都有意义,字就是代号。博客名从前一直叫"Fred Chu's Weblog",当然是不知道该叫什么好才取了这个名,现在叫Oracle One,一是因为有了自己的顶级域名,虽然不是那么牛,几个字母加数字的混合.
但是在这个年代,注册一个简短但又有意思的域名真的太难了,本来想叫做DBA什么的,但是因为Oracle公司现在收购了SUN,所以就注册了oracle1.com这域名,意思就是说Oracle是No1的意思,虽然BLOG内容似乎与Oracle并没什么联系,但是这却成了一个可以填补的空白,就好像这是一支潜力股。
网络的未来属于Web与HTML.
但是在这个年代,注册一个简短但又有意思的域名真的太难了,本来想叫做DBA什么的,但是因为Oracle公司现在收购了SUN,所以就注册了oracle1.com这域名,意思就是说Oracle是No1的意思,虽然BLOG内容似乎与Oracle并没什么联系,但是这却成了一个可以填补的空白,就好像这是一支潜力股。
网络的未来属于Web与HTML.
Tuesday, April 20, 2010
在windows中设置Memcached服务启动参数
[caption id="attachment_1448" align="aligncenter" width="417" caption="memcached"][/caption]
于是就想到直接修改windows服务的启动参数,操作如下,打开注册表,找到:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\memcached Server 其中的ImagePath项的值为: [cci lang='text' line_numbers='false']c:\memcached\memcached.exe" -d runservice[/cci]
改成:[cci lang='text' line_numbers='false']c:\memcached\memcached.exe" -p 12345 -m 128 -d runservice[/cci]
于是就想到直接修改windows服务的启动参数,操作如下,打开注册表,找到:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\memcached Server 其中的ImagePath项的值为: [cci lang='text' line_numbers='false']c:\memcached\memcached.exe" -d runservice[/cci]
改成:[cci lang='text' line_numbers='false']c:\memcached\memcached.exe" -p 12345 -m 128 -d runservice[/cci]
A new munin node client for windows
[caption id="attachment_1452" align="aligncenter" width="305" caption="Munin Monitor"][/caption]I fork a new munin node client for windows this week. everyone can download source, post bug report and download release binary at google code.
Changelogs
- add CIDR network address access (192.168.0.0/24)
- don't send logevent when munin master connect
- add logError function to service.cpp
- add master ipaddress config
- add wether log connections config
- don't rewrite new config file
Monday, April 19, 2010
ping 0xc0a8010a
[caption id="attachment_1454" align="aligncenter" width="548" caption="ping network tool on windows"][/caption][cc lang='text' line_numbers='false']
[fred@home ~]$ ping 0xc0a8010a
PING 0xc0a8010a (192.168.1.10) 56(84) bytes of data.
^C
--- 0xc0a8010a ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2479ms
[/cc]
[fred@home ~]$ ping 0xc0a8010a
PING 0xc0a8010a (192.168.1.10) 56(84) bytes of data.
^C
--- 0xc0a8010a ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2479ms
[/cc]
Tuesday, April 6, 2010
Use fdisk fix hard disk error
Just did a sudo fdisk -l of my newly installed OS. I had manually configured the partitions with the Live CD install to allow for my /home to be on it's own partition. The included screenshot of same indicates that my Partition table entries are not in disk order. Is this something I should correct? Can I expect problems with the partitioning as it is? If so, what should I do?
It is not a problem. You can "reset" them to the correct order but you would need to check your grub menu and fstab in case there were any references to "sdXX" instead of to UUIDs. The reason is at least two of the partition "sdXX" designations would change after you 'reset' them.
For those wishing to do so, here is the procedure. Note that your system will operate fine without making this change and you run the risk of screwing up your boot process or partition mounting if the partition designations no longer match in fstab or menu.lst:
at the prompt:
m (for help)
at the prompt:
x (extra functionality - experts only)
f (fix)
w (write to disk and exit)
You may get a warning that devices are in use and the new table will be used at the next boot.
Check fstab and menu.lst before rebooting.
Repeat for other drives.
It is not a problem. You can "reset" them to the correct order but you would need to check your grub menu and fstab in case there were any references to "sdXX" instead of to UUIDs. The reason is at least two of the partition "sdXX" designations would change after you 'reset' them.
For those wishing to do so, here is the procedure. Note that your system will operate fine without making this change and you run the risk of screwing up your boot process or partition mounting if the partition designations no longer match in fstab or menu.lst:
sudo fdisk /dev/sda
at the prompt:
m (for help)
at the prompt:
x (extra functionality - experts only)
f (fix)
w (write to disk and exit)
You may get a warning that devices are in use and the new table will be used at the next boot.
Check fstab and menu.lst before rebooting.
Repeat for other drives.
Subscribe to:
Posts (Atom)