2012年3月5日 星期一
specify specific rsync binary
I have 64bits rsync 2.6.9 installed in my environment. When remote site triggers file transfer through rsync to my 32 bits platform, system will complain about rsync binary execution error. The reason is the search order in my environment setup. System looks for rsync binary from /usr/local/bin/ first and then /usr/bin/. In order to get this resolve, you have to specify the rsync path when running rsync command.
2012年3月1日 星期四
session stalled when transfer files between two sites with unstable internet connection
net.core.rmem_default = 524288
net.core.rmem_max = 524288
net.core.wmem_default = 524288
net.core.wmem_max = 524288
net.ipv4.tcp_wmem = 4096 87380 524288
net.ipv4.tcp_rmem = 4096 87380 524288
net.ipv4.tcp_mem = 524288 524288 524288
net.ipv4.tcp_rfc1337 = 1
net.ipv4.ip_no_pmtu_disc = 0
net.ipv4.tcp_sack = 1
net.ipv4.tcp_fack = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_ecn = 0
net.ipv4.route.flush = 1
ref: http://ubuntuforums.org/showthread.php?t=891695
net.core.rmem_max = 524288
net.core.wmem_default = 524288
net.core.wmem_max = 524288
net.ipv4.tcp_wmem = 4096 87380 524288
net.ipv4.tcp_rmem = 4096 87380 524288
net.ipv4.tcp_mem = 524288 524288 524288
net.ipv4.tcp_rfc1337 = 1
net.ipv4.ip_no_pmtu_disc = 0
net.ipv4.tcp_sack = 1
net.ipv4.tcp_fack = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_ecn = 0
net.ipv4.route.flush = 1
ref: http://ubuntuforums.org/showthread.php?t=891695
2012年1月9日 星期一
2012年1月6日 星期五
glibc version issue
in order not to upgrade the whole system to support some specific program, you can pull the required library from the compatible system to desired platform and have LD_PRELOAD or LD_LIBRARY_PATH defined before invoking the process.
in bash
LD_PRELOAD="......" glibc.so target_process
lmgrd去跑vendor daemon會有問題
此時僅需暫時修改預設loader,待lmgrd成功啟用後,在改回預設loader即可
in bash
LD_PRELOAD="......" glibc.so target_process
lmgrd去跑vendor daemon會有問題
此時僅需暫時修改預設loader,待lmgrd成功啟用後,在改回預設loader即可
2012年1月5日 星期四
nis map management
nested nfs automount issue
after revising the automap and then push the revised map to clients, nested mount will not appear.
Ans: need to force unmount the map root and restart nfs client
umount -l, fuser -k ....
after revising the automap and then push the revised map to clients, nested mount will not appear.
Ans: need to force unmount the map root and restart nfs client
umount -l, fuser -k ....
2011年12月6日 星期二
asterisk cli kill call
show current channels --> core show channels
hangup a call --> channel request hangup|
hangup a call --> channel request hangup
2011年11月16日 星期三
訂閱：
文章 (Atom)