dpkg --print-architecture

ou encore, niveau noyau :

uname -m

viaconnaitre architecture *hardware* 32 ou 64 bits.

Nov19

2008 Leave a Comment Written by gkoo

The mail command under Debian distros is a part of the mailutils package.

Simply use :

apt-get install mailutils

and you’re done !

viaHowTo : install the mail command under Debian | ItHowTo.ro.

output_handler =

zlib.output_compression = On

viaCompressing PHP Output « Newest Industry.

Firstly create a network bridge that can be placed inbetween the test network and its router.

To increase network latency use the following command:

tc qdisc add dev eth0 root netem delay 2000ms

which will delay every IP packet going through the bridge by 2 seconds.

To reset this delay and remove the 2 seconds of latency:

tc qdisc del dev eth0 root

viaEmulating a high latency network connection using Linux and TC.

iptables -t mangle -A FORWARD -m statistic –mode random –probability 0.01 -j DROP

(where probability is expressed as a value between 0 and 1)

If the intention is to emulate packet drop to the local Linux system not using a bridge, use the INPUT chain:

iptables -t mangle -A INPUT -m statistic –mode random –probability 0.01 -j DROP

To remove the random packet drop and restore the connection to normal operation either change -A to -D in the above commands, or flush the iptables with:

iptables -t mangle -F FORWARD or iptables -t mangle -F INPUT

viaEmulating a network connection with packet drop.

kernel : vga=

Colors ( depth) 640×480 800×600 1024×768 1280×1024 1600×1200 —————+——-+——-+——–+———+———

256 ( 8 bit)| 769 771 773 775 796

32,768 (15 bit)| 784 787 790 793 797

65,536 (16 bit)| 785 788 791 794 798

16.8M (24 bit)| 786 789 792 795 799

viaShrimpWorks » Change your console resolution and colour depth.

Siege is packaged for Debian and Ubuntu, but it doesn’t look to be packaged for Fedora and openSUSE (at least in the default repos). Do remember, though, it’s « i » before « e » — I nearly missed the package for Ubuntu by searching for « seige, » which (obviously) doesn’t exist.

The source, of course, is available. Note that the link to the latest version from the homepage returns an « unable to connect » error (at least as of this writing). However, the pub directory is available over HTTP even if the FTP server seems to be down.

Once installed, Siege is very easy to use. You can use Siege to test over HTTP and HTTPS — it has no support for FTP or other protocols at the moment.

To start with, you probably want to generate a Siege configuration file. You can generate a template quickly using siege.config, which will drop a file called .siege.rc in your home directory. Here, you can set many of the options for Siege, like the output format (including a CSV output rather than the older Siege format), how many concurrent users to simulate, duration, and so on. If you have fairly standard testing parameters, you can store them in the config rather than using them on the command line or specifying them in a script. If you want to use an alternative configuration file, use export SIEGERC=/filename or siege -R siegerc.

One thing Siege is good for is grabbing the HTTP headers quickly. If you just want to see HTTP headers, run siege -g URL. Note that the URL must be the server name only if you just want to see what a server is running, or a full URL if you want to hit specific resources.

Now, let’s look at a sample test using siege. Say you want to simulate 50 users hitting the resource simultaneously, with a delay of up to 10 seconds between requests:

siege -d10 -c50 http://mysite.com/blog/blah.php

The -d option specifies the delay, while the -c option tells siege how many users it should simulate. Note that the -d option is a random interval between 0 and X seconds, with X being the number of seconds you specify — so if you say 10 seconds, it may be 0 seconds, it may be 4 seconds, and so on — it just won’t be longer than 10.

If you want to give a site a real workout, you probably want to specify more than one URL. You can do this with a list of URLs in ~/etc/urls.txt or specify a text file with URLs using the -f file option. If you want a simulation closer to real-world usage, you’ll want to use the -i option, which hits the URLs in the file randomly.

A fairly good template for testing might be:

siege -d10 -c50 -i -f mysite.txt

Be careful using Siege against production sites — especially dinky little VPSes with very little RAM. Not that I’d know from personal experience or anything. It should also go without saying that you should not use Siege against sites you’re not responsible. At best, doing so is impolite, but it could also be a violation of your ISP’s terms of service, and at worst it may be illegal.

viaLoad Testing and Benchmarking With Siege.

Par Jérôme Pouiller le vendredi, octobre 29 2010, 09:37 – Lien permanent

As you may know, you have juste to add options ARCH and if necessary CROSS_COMPILE to command line:

make ARCH=powerpc CROSS_COMPILE=ppc-linux-gnu- XXX_defconfig

make ARCH=powerpc CROSS_COMPILE=ppc-linux-gnu- XImage

My primary concern is to compile an x86 32bits kernel in 64bits environement. So my compilation line is:

make ARCH=i386 i386_defconfig

make ARCH=i386 bzImage

As you also may know, rule deb-pkg of kernel Makefile is able to create a debian package. You should use fakeroot to be able to create package with a non-root user:

fakeroot make deb-pkg

Nevertheless, it will always create a package for current architecture. So this line will create a package for powerpc:

fakeroot make ARCH=powerpc CROSS_COMPILE=ppc-linux-gnu- deb-pkg

To correct this behavior, you can use DEB_HOST_ARCH variable:

fakeroot make DEB_HOST_ARCH=powerpc ARCH=powerpc CROSS_COMPILE=ppc-linux-gnu- deb-pkg

To summary, to quickly create an x86 32bits kernel debian package in 64bits environement. I do:

mkdir build

make ARCH=i386 O=build i386_defconfig

fakeroot make -j4 DEB_HOST_ARCH=i386 ARCH=i386 O=build deb-pkg

viaBuild cross-compiled kernel debian package – Sysmic.org.

In search for a lightweight solution to run some php pages on my Debian diskless shellserver it appears there are several lightweight httpd daemons in Debian that can do php.

I created some virtual machines on KVM to do some testing. Here follows a short howto to get the different httpd servers running

Howto install lightweigt httpd daemons with PHP support

Debian comes with several httpd daemons. On this page we look at the following httpd servers:

Lighthttpd

Cherokee

Nginx

Nginx requires the most work.

Lighthttpd with PHP

apt-get install mysql-server mysql-client

apt-get install lighttpd

comment this line out in /etc/lighttpd/lighttpd.conf include_shell « /usr/share/lighttpd/use-ipv6.pl »

check that lighthttpd is running.

Point your browser to http://<ip-number>

screenshot of lighttpd

Screenshot of lighttpd just after installing

apt-get install php5-cgi

ln -s /etc/lighttpd/conf-available/10-fastcgi.conf /etc/lighttpd/conf-enabled/

/etc/init.d/lighttpd restart

PHP ready to use

Your server should be ready to use PHP now. To test it, create a file info.php in /var/www. The contents of the file should be something like this:

<?

phpinfo();

?>

screenshot of lighttpd running php info

Screenshot of lighttpd running phpinfo

Cherokee with PHP

apt-get install mysql-server mysql-client

apt-get install cherokee

apt-get install php5-cgi

test that cherokee runs, point your browser to http://<ip-number>

screenshot of cherokee

Screenshot of cherokee just after installing

Run cherokee-admin -b

The -b option makes it possible to reach cherokee-admin from other machines than localhost.

screenshot of cherokee admin

Screenshot of cherokee admin

Click on Virtual servers

Click on « default »

Click on « Wizzards »

Click on « Languages »

Click on « Run Wizzard » next to the PHP logo

(See screenshot below)

screenshot of cherokee admin ready to invoke php wizzard

Screenshot of cherokee admin ready to invoke the PHP-wizzard

PHP ready to use

Your server should be ready to use PHP now. To test it, create a file info.php in /var/www. The contents of the file should be something like this:

<?

phpinfo();

?>

screenshot of cherokee running php info

Screenshot of cherokee running phpinfo

viaRun PHP with a light weight webserver | box.matto.nl.