http://technet.microsoft.com/en-us/library/cc938217.aspx
http://support.microsoft.com/kb/2634328
http://technet.microsoft.com/en-us/library/cc938217.aspx
http://technet.microsoft.com/en-us/library/cc938217.aspx
http://support.microsoft.com/kb/2634328
http://technet.microsoft.com/en-us/library/cc938217.aspx
using telnet
$ telnet 127.0.0.1 11211
Trying 127.0.0.1…
Connected to localhost.
Escape character is ‘^]’.
flush_all
OK
quit
Connection to localhost closed by foreign host.
$
using netcat
echo “flush_all” | /bin/netcat -q 2 127.0.0.1 11211
I have had many issues on freelancer.com related to unpaid jobs from an newbies employers for last 3 years which I working on freelancer.com site. The last one problem related to money on freelancer.com … totally destroyed my patience and silence. I had think I need to share my bad experience for other freelancers which want to work or begin working on freelancer.com. They should know they are un-protected on freelancer.com and money can go from your account anytime by many reasons.
My Nick Name : stels88
My Profile Page : http://www.freelancer.com/u/stels88.html
Project URL https://www.freelancer.com/projects/System-Admin-Linux/WHM-cPanel-Server-directory-quot.html
Employer Profile Page : https://www.freelancer.com/u/marioshyti.html
Employer Mobile Phone Number : +353873691403
Employer Skype Login : mariostutorials
Employer Site : www.4ost.eu
Price 45 USD.
Time Spent 6 h.
Payment received only for 75% from initial price of 45 USD.
Payment of 75% was canceled by freelancer.com staff and refunded from my budget to Employer account without of any notification email, with no reason at Payments HISTORY page.
Result… 6 working hours spent at nigh was spent for -4.00 USD from my balance as project fee, profit -4 USD
to read more complains related to freelancer.com you can visit the following url
http://www.reviewopedia.com/freelancer-com-reviews
finally…here is what I can think about freelancer.com is possible to say in two words…. freelancer.com SUCKS!!!
http://ark.intel.com/ru/products/59470/Intel-Centrino-Advanced-N-6200-Dual-Band
[root@localhost stealth]# lspci -nn|grep Network
09:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6200 [8086:422c] (rev 35)
[root@localhost stealth]#
[root@localhost stealth]# uname -r
3.8.4-1-ARCH
[root@localhost stealth]#
[root@localhost iwlwifi]# pacman -Qo /lib64/modules/`uname -r`/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko.gz
/lib64/modules/3.8.4-1-ARCH/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko.gz принадлежит linux 3.8.4-1
[root@localhost iwlwifi]#
[root@node01 ~]# rm -rf /var/spool/exim/db/retry*
[root@node01 ~]# rm -rf /var/spool/exim/db/wait-remote_smtp*
[root@node01 ~]# /etc/init.d/exim restart
1. BigBlueButton do not support CentOS anymore
http://code.google.com/p/bigbluebutton/wiki/FAQ#CentOS
2. BigBlueButton has dependecies problem on Ubutun 12.10, that’s why installation can be done on the fly only on 10.04
http://code.google.com/p/bigbluebutton/wiki/InstallationUbuntu#Before_you_install
cd /usr/local/src/
mkdir -pv bbb && cd bbb
# Add the BigBlueButton key
wget http://ubuntu.bigbluebutton.org/bigbluebutton.asc -O- | sudo apt-key add
# Add the BigBlueButton repository URL and ensure the multiverse is enabled
echo "deb http://ubuntu.bigbluebutton.org/lucid_dev_08/ bigbluebutton-lucid main" > /etc/apt/sources.list.d/bigbluebutton.list
echo "deb http://ubuntu.mirror.cambrium.nl/ubuntu/ lucid main" >> /etc/apt/sources.list.d/bigbluebutton.list
echo "deb http://us.archive.ubuntu.com/ubuntu/ lucid multiverse" >> /etc/apt/sources.list
sudo apt-get update
sudo apt-get dist-upgrade
yum install icu libicu libicu-devel
cd /usr/local/directadmin/custombuild
./build used_configs
Edit your PHP 5 config file, related to configuration you can have ap2 or suphp:
vi /usr/local/directadmin/custombuild/configure/ap2/configure.php5
or
mkdir -pv custom/ap2
cp -v configure/ap2/configure.php5 custom/ap2/configure.php5
vi /usr/local/directadmin/custombuild/custom/ap2/configure.php5
vi /usr/local/directadmin/custombuild/configure/suphp/configure.php5
or
mkdir -pv custom/suphp
cp -v configure/suphp/configure.php5 custom/suphp/configure.php5
vi /usr/local/directadmin/custombuild/custom/suphp/configure.php5
NOTE: that only the last rule has no slash!)
--enable-intl
Save the file and rebuild PHP with executing next commands:
./build clean
./build update
./build php all
cd /usr/local/directadmin/custombuild
./build used_configs
Edit your PHP 5 config file, related to configuration you can have ap2 or suphp:
vi /usr/local/directadmin/custombuild/configure/ap2/configure.php5
or
mkdir -pv custom/ap2
cp -v configure/ap2/configure.php5 custom/ap2/configure.php5
vi /usr/local/directadmin/custombuild/custom/ap2/configure.php5
vi /usr/local/directadmin/custombuild/configure/suphp/configure.php5
or
mkdir -pv custom/suphp
cp -v configure/suphp/configure.php5 custom/suphp/configure.php5
vi /usr/local/directadmin/custombuild/custom/suphp/configure.php5
NOTE: that only the last rule has no slash!)
--with-xmlrpc
Save the file and rebuild PHP with executing next commands:
./build clean
./build update
./build php all
If you run a firewall on your Linux server and want to use passive FTP connections, you have to define the passive port range for FTP Server plus whitelist these ports in firewall. Recommended to use highest possible port sent to the FTP clients for passive mode connections, in our example we will use IANA registered ephemeral port range 49152-65534.
1. apply changes to FTP server.
2. apply changes to iptables firewall
3. save changes for iptables firewall
for pure-ftpd you can change ftp passive port range via /etc/pure-ftpd.conf
PassivePortRange 49152 65534
for vsftpd you can change ftp passive port range via /etc/vsftpd.conf
pasv_min_port=49152
pasv_max_port=65534
now we need to whitelist passive port range for iptables firewall in order to allow connections to these ports with no restrictions :
iptables -I INPUT -p tcp --dport 49152:65534 -j ACCEPT
after we added passive port range to iptables, we need to save changes to make them permanent and working the same with next system reboot, so simply issue the following command to save changes to iptables init configuration file.
/etc/init.d/iptables save