Now these days best and attractive images are the part of every articles. I can say image is useful for your posts. Images made easy to understand to readers what you want to say in the post. Here we given the list of resources where you get free image for wordpress posts
Many wordpress blogger go to google for images and find the images. They put the image into their blogs. Some time that will cause you serious legal issues.
where we get free image for wordpress posts
where we get free image for wordpress posts
There are very good places to find good free images for your blogs. Here is the list of that.
Flickr: Flickr is a really great source for free pics, however make sure to contact the owner of the picture and ask permission before using it. I have done this a lot in the past and a lot of people are willing to share their pictures. Give them a good reason, maybe a quick complement and offer a link back to their Flickr profile.
Stockvault: Stockvault has a lot of nice stock photos, just be warned that this site is filled with adsense.
deviantART: This is a huge community of artist sharing all sorts of images and graphics. Again, checkout the license of the graphic as a lot of these aren’t free, yet it is still a great source for free images if you become familiar with the site.
Stock.xchng: Saving the best for last here you’ll be able to find a lot of great stock photos as well as PSD’s, templates, background images and more. Please checkout the restrictions before using
Free Images – Free Stock Photos: FREE digital photographic images for web, dtp, and design. Royalty and cost-free stock photos. Free stock photographic library.
gettyimages: Getty Images royalty-free gives creative freedom to crop, manipulate and combine stock photos for your project needs. Simple, affordable pricing, unlimited use.”
WordPress has just announced the 100th million plugin has now been downloaded. It’s a smaller milestone but just as impressive if not even more so, since blogging tools are not going to have the same mainstream audience or appeal as a web browser. WordPress is also celebrating a smaller milestone, the newly launched WordPress 3.0 has just passed three million downloads.
WordPress completed 100th Million Plugin Download
WordPress completed 100th Million Plugin Download
What wordpress is saying?
WordPress 3.0 Thelonious passed 3 million downloads yesterday, and today the plugin directory followed suit with a milestone of its own: 100 million downloads.
The WordPress community’s growth over the years has been tremendous, and we want to reinvest in it. So we’re taking the next two months to concentrate on improving WordPress.org. A major part of that will be improving the infrastructure of the plugins directory. More than 10,000 plugins are in the directory, every one of them GPL compatible and free as in both beer and speech. Here’s what we have in mind:
We want to provide developers the tools they need to build the best possible plugins. We’re going to provide better integration with the forums so you can support your users. We’ll make more statistics available to you so you can analyze your user base, and over time we hope to make it easier for you to manage, build, and release localized plugins.
We want to improve how the core software works with your plugin and the plugin directory. We’re going to focus on ensuring seamless upgrades by making the best possible determinations about compatibility, and offer continual improvements to the plugin installer. And we also want to give you a better developer tool set like SVN notifications and improvements to the bug tracker.
We’re also going to experiment with other great ideas to help the community help plugin authors. We want it to be easy for you to offer comments to plugin authors and the community, including user reviews and better feedback. We may experiment with an adoption process for abandoned plugins as a way to revitalize hidden gems in the directory. I’m not sure there is a better way to show how extendable WordPress is and how awesome this community is at the same time.
As Matt said in the 3.0 release announcement, our goal isn’t to make everything perfect all at once. But we think incremental improvements can provide us with a great base for 3.1 and beyond, and for the tens of millions of users, and hundreds of millions of plugin downloads to come.
There are now a little over 10,000 plugins in the WordPress directory which really puts the 100 million downloads number in perspective. Of course, some plugins are more popular than others, but it does indicate that bloggers are very interested in the added functionality these plugins provide.
The most popular plugin is the antispam tool Akismet with over 8.5 million downloads to date. The tool comes pre-installed with WordPress, so that may explain its popularity, although, these installs may not be counted as downloads. However, later updates are probably counted. Other popular plugins are the All in One SEO Pack with five million downloads and Google XML Sitemaps with close to four million.
Given the popularity of WordPress plugins, it’s no surprise that they are now getting some attention from the development team. Having wrapped up WordPress 3.0, the team decided to focus on some of the things surrounding WordPress rather than the software itself.
“The WordPress community’s growth over the years has been tremendous, and we want to reinvest in it. So we’re taking the next two months to concentrate on improving WordPress.org. A major part of that will be improving the infrastructure of the plugins directory,” Andrew Nacin, a WordPress developer, announced.
“We’re going to provide better integration with the forums so you can support your users. We’ll make more statistics available to you so you can analyze your user base, and over time we hope to make it easier for you to manage, build, and release localized plugins,” he explained.
Here in this article we given history of mozilla firefox. We tested our site with every firefox version and given the sanup shots. The The Mozilla Firefox project was created by Dave Hyatt and Blake Ross as an experimental branch of the Mozilla project.
Firefox 1.0 was released on November 9, 2004. Firefox 1.5 was released on November 29, 2005. Version 2.0 was released on October 24, 2006 and Firefox 3.0 was released on June 17, 2008. Version 3.5 was released on June 30, 2009 and Version 3.6 was released on January 21, 2010.
Hyatt, Hewitt and Ross’s browser was created to combat the perceived software bloat of the Mozilla Suite (codenamed, internally referred to, and continued by the community as SeaMonkey), which integrated features such as IRC, mail and news, and WYSIWYG HTML editing into one software suite.
Firefox retains the cross-platform nature of the original Mozilla browser, using the XUL user interface markup language. The use of XUL makes it possible to extend the browser’s capabilities through the use of extensions and themes. The development and installation processes of these add-ons raised security concerns, and with the release of Firefox 0.9, the Mozilla Foundation opened a Mozilla Update website containing “approved” themes and extensions. The use of XUL sets Firefox apart from other browsers, including other projects based on Mozilla’s Gecko layout engine and most other browsers, which use interfaces native to their respective platforms (Galeon and Epiphany use GTK+; K-Meleon uses MFC; and Camino uses Cocoa). Many of these projects were started before Firefox, and probably served as inspiration.
Although the Mozilla Foundation had intended to make the Mozilla Suite obsolete and to replace it with Firefox, the Foundation continued to maintain the suite until April 12, 2006[1] because it had many corporate users, as well as being bundled with other software. The Mozilla community (as opposed to the Foundation) continues to release new versions of the suite using the product name SeaMonkey to avoid any possible confusion with the original Mozilla Suite.
On February 5, 2004 the business and IT consulting company AMS categorized Mozilla Firefox (then Firebird) as a “Tier 1” (meaning “Best of Breed”) open source product.[2] This meant that AMS considered Firebird (as it was called at the time) to be virtually risk-free and technically strong.
history of mozilla firefox
Phoenix 0.1, the first official release.
history of mozilla firefox
Firefox 1.0, the first release targeted for general public.
The project which became Firefox started as an experimental branch of the Mozilla Suite called m/b (or mozilla/browser). When sufficiently developed, binaries for public testing appeared in September 2002 under the name Phoenix.
The Phoenix name was retained until April 14, 2003 when it was changed (after a short stint as Phoenix Browser) due to trademark issues with the BIOS manufacturer, Phoenix Technologies (who produce a BIOS-based browser called Phoenix FirstWare Connect). The new name, Firebird, was met with mixed reactions, particularly as the Firebird database server already carried the name. In late April, following a name change to Firebird browser (which lasted only a few hours), the Mozilla Foundation issued an official statement which stated that the browser should be referred to as Mozilla Firebird (as opposed to just Firebird). Continuing pressure from the Firebird community forced another change, and on February 9, 2004 the project was renamed Mozilla Firefox (or Firefox for short).
The name, “Firefox”, was chosen for its similarity to “Firebird”, but also for its uniqueness in the computing industry. To ensure that no further name changes would be necessary, the Mozilla Foundation began the process of registering Firefox[3] as a trademark with the United States Patent and Trademark Office in December 2003. This trademark process led to a delay of several months in the release of Firefox 0.8 when the foundation discovered that in the UK Firefox had already been registered[4][dead link] as a trademark for software by The Charlton Company.[5] The situation was resolved when the foundation was given a license to use Charlton’s European trademark.
Early Firebird and Phoenix releases of Firefox were considered to have had reasonable visual designs, but were not up to the same standard as many professionally released software packages. In October 2003, professional interface designer, Steven Garrity, wrote an article covering everything he considered to be wrong with Mozilla’s visual identity.[6] The page received a great deal of attention. The majority of the criticisms levelled at the article were along the lines of “where’s the patch?”
Shortly afterwards, Garrity was invited by the Mozilla Foundation to head up the new visual identity team. The release of Firefox 0.8 in February 2004 saw the introduction of the new branding efforts, including new icons designed by silverorange, a group of web developers with a long-standing relationship with Mozilla, with final renderings by Jon Hicks, who had previously worked on Camino.[8][9] The logo was revised and updated later, fixing some flaws found when the logo was enlarged.[10]
The animal shown in the logo is a stylized fox, although “firefox” is considered to be a common name for the Red Panda. The panda, according to Hicks, “didn’t really conjure up the right imagery”, besides not being widely known.[9] The logo was chosen for the purpose of making an impression, while not shouting out with overdone artwork. The logo had to stand out in the user’s mind, be easy for others to remember and stand out while not causing too much distraction when among other icons. It was expected to be the final logo for the product.
The Firefox icon is a trademark used to designate the official Mozilla build of the Firefox software, and builds of official distribution partners.[11] For this reason, Debian and other software distributors who distribute patched or modified versions of Firefox do not use the icon. The crash reporting service was previously closed-source, but switched with version 3, going from a program called Talkback, to the open source BreakPad & Socorro.
history of mozilla firefox
Various logos used during the development of Firefox.
history of mozilla firefox
Blue globe artwork is distributed with Firefox source code, and is explicitly not protected as a trademark.
Early Firefox releases featured a preferences panel that described cookies by stating “Cookies are delicious delicacies”.
The phrase was representative of the programmers’ quirky sense of humor and a general reflection of the free software movement’s unconventional approach. The phrase became something of a cult legend and was even featured in an O’Reilly computer book.
The original text was inserted by Blake Ross, one of the lead developers of Firefox, because, he says, “describing something so complicated in such a small space was quite frankly the last thing I wanted to worry about after rewriting the cookie manager”.
However, in reflection of the growing acceptance and use of the Firefox browser in the Internet mainstream, the text was later changed. It was considered[12] a bug and was “fixed” by Mike Connor to read “Cookies are pieces of information stored by web pages on your computer. They are used to remember login information and other data”. The revision was regarded as more likely to be helpful for the less technically oriented computer users who were now using Firefox—representing Mozilla’s desire to appeal to mainstream users.
After this happened, the following remarks were made by Blake Ross over IRC to Mike Connor:
congratulations mconnor
you just destroyed a legend!
The text became a popular in-joke and on August 2004, the Delicious Delicacies extension, which is no longer maintained and updated, was released by Jesse Ruderman. This extension restored the old description of cookies, available in several languages.
As of Firefox 2.0, cookies no longer have a description in the preferences window.
On June 23, 2005, the Mozilla Foundation announced that Firefox 1.1 (which became Firefox 1.5) and other new Mozilla products will no longer support Mac OS X v10.1. This is intended to improve the quality of Firefox releases on Mac OS X v10.2 and above. Users of 10.1 could still use Firefox versions from the 1.0.x branch (e.g. Firefox 1.0.7).
Firefox 1.5 was released on November 30, 2005. The original plan was for a Firefox 1.1 and later a Firefox 1.5. After the first two 1.1 alpha builds, the Mozilla Foundation abandoned the 1.1 release plan and merged it with the planned feature set of 1.5 instead, with 1.5 being released later than was planned for 1.1. The new version resynchronised the code-base of the release builds (as opposed to nightly builds) with the core “trunk” which contained additional features not available in 1.0, as it branched from the trunk around the 0.9 release. As such, there was a backlog of bug fixes between 0.9 and the release of 1.0, which were made available in 1.5. Version 1.5 implemented a new Mac-like options interface, which was the subject of much criticism from Windows and Linux users, with a “Sanitize” action to allow a person to clear their privacy related information without manually clicking the “Clear All” button. In Firefox 1.5, a user can clear all privacy-related settings simply by exiting the browser or using a keyboard shortcut, depending on their settings. Moreover, the software update system was improved (with binary patches now possible). There were also improvements in the extension management system, with a number of new developer features.
Also, Firefox 1.5 had preliminary SVG 1.1 support.[13] This unplanned movement may have been due to the release of Opera 8.0 on April 19, 2005, which supported SVG Tiny.[speculation?]
Alpha builds of Firefox 1.5 (1.1a1 and 1.1a2) did not contain Firefox branding. They were labeled “Deer Park” (which was Firefox 1.5’s internal codename) and contained a different program icon. This was done to dissuade end-users from downloading preview versions, which are intended for developers only.
Firefox 1.5.0.12 is the final version supported on Windows 95.
“Deer Park”, the codename of the Firefox 1.1 and 1.5 Alphas, did not include Firefox branding.
On March 22, 2006, the first alpha version of Firefox 2 (Bon Echo Alpha 1) was released. It featured Gecko 1.8.1 for the first time.
Firefox 2 was released on October 24, 2006 and contained many new features not found in Firefox 1.5, including improved support for SVG and JavaScript 1.7, as well as UI changes.
Mozilla Firefox 2.0.0.x is the final version supported on Windows NT 4.0, 98 and Me. Mozilla Corporation has announced that it will not develop new versions of Firefox 2 after the 2.0.0.20 release. They did however continue development of Firefox 2 as long as other programs, like the Thunderbird mail client, were depending on it. The final internal release was 2.0.0.22, released in late April 2009.
In December 2007, Firefox Live Chat was launched. It allows users to ask volunteers questions with hours of operation and the possibility of help after hours. Because this service is kept running because of volunteers, if there are not enough volunteers to help, they may not open during the official hours.
The Mozilla Foundation released Firefox 3 on June 17, 2008. The first Firefox 3 beta (under codename ‘Gran Paradiso’). had been released several months earlier on 19 November 2007, which was followed by several more beta releases in the Spring of 2008 culminating in the June release.
One of the major changes in Firefox 3 is the implementation of Gecko 1.9, an updated layout engine. The new version fixes many bugs and implements new web APIs.
After several development releases, the final version was released on June 30, 2009. The current version is 3.5.10, released on June 22, 2010. Also, as of mid-December 2009, Firefox 3.5 is the most popular browser (when counting individual browser versions) passing Internet Explorer 7. It is the first version to accomplish this feat.
Version 3.6, released on January 21, 2010, uses the Gecko 1.9.2 engine and includes several interface improvements, such as “personas.” This release was referred to as 3.2 before 3.1 was changed to 3.5. The codename for this version was Namoroka.
One minor update to Firefox 3.6, version 3.6.4 (code-named Lorentz) is the first minor update to make non-intrusive changes other than minor stability and security fixes. It adds Out of Process Plugins (OOPP), which runs plugins in a separate process, allowing Firefox to recover from plugin crashes.
As part of Mozilla’s ongoing stability and security update process, Firefox 3.6.6 is now available as a free download for Windows, Mac, and Linux from http://www.firefox.com. This release makes a small change to the crash protection feature introduced in Firefox 3.6.4, increasing the amount of time that Firefox will allow a plugin to remain frozen before terminating it. For more information, see the Mozilla Blog announcement about the release.
The precursory releases of upcoming Firefox releases are codenamed “Minefield”, as this is the name of the trunk builds. As of June 2010, development for Firefox 4 takes place on the Mozilla trunk, with pre-release builds coming nightly.
Version 4.0
Nightly builds were marked as 4.0a1pre between February and June of 2008,[21][22] but were renamed to 3.1a1pre afterward.
Firefox 3.7 (Gecko 1.9.3) Alpha 1 was released on February 10, 2010.[23][24] Alpha 2 was released on March 1, 2010, Alpha 3 was released on March 17, and Alpha 4 was released on April 12, 2010. As of May 2010, Alpha 5 is being developed on the trunk. The version number 3.7 is a placeholder; this release is now planned to be Firefox 4.0 and is tentatively scheduled for November 2010.[25]
One of the main focuses is to improve the user interface. Mockups of a UI overhaul for the Windows version have been posted in the Mozilla Wiki. They show plans for many changes, including optionally display the tabs bar at the top of the window, integrating the status bar into the tab toolbar and integrating the search bar and the reload and stop buttons into the awesomebar.[26] The menu bar is not present in these mockups. The UI will use animations for manipulating tags and buttons.
The browser will be given a home tab. This will be similar to the new tab pages found in Internet Explorer 8 and Google Chrome. However, users are able to customise the button so that it takes the user to their homepage instead.
The installer on the Mac OS X will be redesigned to make installations easier. Also, the start up windows that appear when Firefox starts up will be eradicated to make the start up process quicker.
The preferences and add-ons manager windows will also be redesigned to better assist users.
“Door hanger” notifications will be added. This is to replace the current “bar” notifications, which can easily be spoofed by a web page.
The Gecko layout engine will be improved to support more HTML5 and CSS3 features.
As well as this, the Firefox Sync project will be integrated into the browser to allow users to sync things such as bookmarks and history with the cloud.
A new type of tab, called an application tab, can be placed in the tab bar. It is similar to the Mozilla Prism project, which allows web pages (such as Google Mail) to become applications.
6 free seo tools from google, SEO is very important when you are building and maintaining a website, and Google offers FREE tools to help make your job easier.
6 free seo tools from google
6 free seo tools from google
Google provides very nice free SEO tools here is list.
According to the website, Google Analytics gives you rich insights into your website traffic and marketing effectiveness. User friendly features allow you to see and analyze your traffic data in a whole new way, as well as produce better targeted ads, create higher converting websites and strengthen your marketing initiatives.
With Google Trends, you can compare the whole world’s interest in the topic of your choice. You can enter up to 5 topics to see how often they have been searched, how often they show up in Google News stories and what geographic locations have searched these topics the most. Google Keyword Tool:
Undoubtedly one of the most popular in the Google toolbox, the Keyword Tool can be a gigantic help in choosing the right and most effective keywords!
Google Website Optimizer:
A very easy to use free tool for testing your website content to see if it is delivering actionable results. You can find out what leads to the highest conversion rates, listen to your visitors and increase conversions dramatically. A great free tool! Google Webmaster Tools:
This one gives you detailed reports about your web pages’ visibility in Google search. You can see at a glance how Google crawls and indexes your site, as well as find out about problems Google is having with your site and how to fix them. You can also use the free link reporting tools and query traffic to see which search queries are driving traffic to your site.
This one will come in quite handy as it tells you such important things as average estimated CPC, estimated ad position, estimated daily cost and estimated daily clicks.
Today, Mozilla is happy to release Firefox 3.6.4, the latest security and stability release for Firefox, used by nearly 400 million people around the world to browse the Web. This release provides crash protection for Windows and Linux users by isolating third-party plugins when they crash.
Results from our beta testing show Firefox 3.6.4 will significantly reduce the number of Firefox crashes experienced by users who are watching online videos or playing games. When a plugin crashes or freezes while using Firefox, users can enjoy uninterrupted browsing by simply refreshing the page.
Mozilla recognizes that third-party plugins provide important functionality in many of today’s websites. At the same time, plugins can lead to problems for users as they browse. With the ability to automatically alert users when they have out of date plugins, and now crash protection, Firefox 3.6.4 allows users to experience all the content they love without any of the hassles. (If you’re not running Firefox, Mozilla recommends that you make a habit of visiting the Plugin Check page to keep your plugins up to date.)
At this time Firefox offers crash protection for Adobe Flash, Apple Quicktime and Microsoft Silverlight on Windows and Linux computers. Support for other plugins and operating systems will become available in a future Firefox release.
All Firefox users are encouraged to upgrade for free by using the “Check for Updates” function in the Help menu, or by visiting www.firefox.com. For more information, please visit:
Google Voice is now available for everyone (provided you have a U.S. phone number).
The service, which started life out as GrandCentral, acts as a unified phone number. It can be used to make free calls to the U.S. and Canada, to send free text messages and more. Its voicemail system can even be.
Now, after more than fifteen months of testing with invite-only accounts, Google Voice is ready for the masses.
As great as the service is, it hasn’t existed without controversy. Last summer, Apple was criticized when the company barred the Google Voice iPhone app from its App Store. The battle over Google Voice was arguably the first shot in the current Apple-Google war.
And earlier today, Business Week reported that Frontier Communications is suing Google over alleged patent violations within the Google Voice service.
For many users however, Google Voice is a wonderful solution to the increasingly complex web of communication profiles. Instead of having to try to maintain separate phone numbers, users can just have one central number forwarded to different devices based on time of day or location.
Jmeter is basically used for load testing of web applications. Application Load testing is very important for every application. Jmeter is loved by every QA and testing software professional. If you are QA software professional then you need to know how install on windows or linux box and how use it properly. Here In this tutorial I shown you to how to Jmeter on Linux.
how to install Jmeter on Linux
install Jmeter on Linux
JMeter is to first download the latest production release and install it. The release contains all of the files you need to build and run most types of tests, e.g. Web (HTTP/HTTPS), FTP, JDBC, LDAP, Java, and JUnit.
If you want to perform JDBC testing, then you will, of course, need the appropriate JDBC driver from your vendor. JMeter does not come with any JDBC drivers.
If you want to install the jmeter on your linux box you need to follow my steps:
[viral-lock message=”Installation steps are Hidden! It’s Visible for Users who Liked/Shared This article on Facebook or Twitter or Google+. Like or Tweet this article to reveal the content.”]
1) Goto http://jakarta.apache.org/site/downloads/downloads_jmeter.cgi
2) Download Binary 2.3.4.zip . The zip file name will be “jakarta-jmeter-2.3.4”
3) Paste it in /var/www/html/
4) Unzip “jakarta-jmeter-2.3.4”
5) New folder with name “jakarta-jmeter-2.3.4” will be created
6) Go to command prompt
7) go to “jakarta-jmeter-2.3.4” folder (cd /var/www/html/jakarta-jmeter-2.3.4)
8) go to “bin” folder (cd bin)
9) Now you are in bin folder (i.e /var/www/html/jakarta-jmeter-2.3.4/bin/)
10) type the command “sh jmeter”
11) After a short pause, the JMeter GUI should appear.
[/viral-lock]
After this you can use following commands for load testing.
For non-interactive testing, you may choose to run JMeter without the GUI. To do so, use the following command options
-n This specifies JMeter is to run in non-gui mode
-t [name of JMX file that contains the Test Plan].
-l [name of JTL file to log sample results to].
-r Run the test in the servers specified by the JMeter property “remote_hosts”
-R [list of remote servers] Run the test in the specified remote servers
The script also lets you specify the optional firewall/proxy server information:
-H [proxy server hostname or ip address]
-P [proxy server port]
Woe to the WordPress administrator who finds only blank pages where once stood a WordPress-based blog or Web site. The site has been plagued with what an increasing number of WordPress operators are nicknaming the White Screen of Death.
Beware the WordPress white screen of death
As the nickname states, the White Screen of Death, WSoD, renders all the WordPress-built pages as a blank screen. But unlike the infamous Microsoft Windows Blue Screen of Death after which it was named, the WSoD does not offer any debugging code, or pointers to what might be causing the problem. Just a blank page where content once resided.
Worse yet, in addition to offlining a Web site or set of blog pages, the bug can also render invisible the WordPress Web-based administrator console, in which some debugging could occur.
The true cause of WSoD cannot be traced to any individual cause, or even to the WordPress code itself, but rather to a conflation of issues around the technology WordPress uses, as well as how the software is augmented by others.
“Our hands … are mostly tied here, especially since WordPress is extended through code from others,” said Andrew Nacin, a WordPress developer, in an e-mail interview.
The good news is that the developers of WordPress offer some simple hints at how to debug the problem, and they promise more measures to thwart the appearance of blank screens in the upcoming version 3.0 release of the software, which should be posted within a few weeks.
Since its first release in 2003, WordPress has played a pivotal role in the emergence of blogs on the Web. An open-source project, it is free to download, and Redwood City, California-based Automattic offers a hosted version of the blogging software, which runs more than 11 million blogs.
Organizations are also considering using WordPress as a low-cost content management system.
WordPress is a modular program. It is actually built with other open-source tools, most notably the PHP Web scripting language. In order to construct a WordPress page, the Web server software executes a series of PHP scripts using a PHP processing module, drawing the content from a database, usually MySQL.
While the WordPress package offers the basic ability to run a blog, most of the additional functionality comes from plug-ins developed by third-parties. Likewise, the look-and-feel of a WordPress blog can be altered by using themes, or templates also generated by third parties.
Some of these of plugs-ins and themes are better constructed than others. And that's where the problem begins.
“Generally, you'll see [a blank page] when PHP hits a brick wall before the browser is served any output,” Nacin said.
In this article I given step by step information about How to install siege on Linux box. I given the full commands and there output with full description.
How to install siege on Linux box
ABOUT SIEGE – Background
Siege is an http load testing and benchmarking utility. It was designed to let web developers measure their code under duress, to see how it will stand up to load on the internet. Siege supports basic authentication, cookies, HTTP and HTTPS protocols. It lets its user hit a web server with a configurable number of simulated web browsers. Those browsers place the server “under siege.”
How to install siege on Linux box
PLATFORM SUPPORT
Siege was written on GNU/Linux and has been successfully ported to AIX, BSD, HP-UX and Solaris. It should compile on most System V UNIX variants and on most newer BSD systems. Because Siege relies on POSIX.1b features not supported by Microsoft, it will not run on Windows. Of course you can use Siege to test a Windows HTTP server.
Download siege from following URL or Using following command
[kapil@kapil-pc ~]$ wget ftp://ftp.joedog.org/pub/siege/siege-latest.tar.gz
[kapil@kapil-pc ~]$ tar xzf siege-latest.tar.gz
[kapil@kapil-pc ~]$ mv siege-2.69 siege
[kapil@kapil-pc ~]$ cd siege
[kapil@kapil-pc siege ~]$ su
[root@kapil-pc siege ~]$ ROOT_PASSWORD
[root@kapil-pc siege ~]$ ./configure
checking for a BSD-compatible install… /usr/bin/install -c
checking whether build environment is sane… yes
checking for gawk… gawk
checking for gcc… no
checking for cc… no
checking for cc… no
checking for cl… no
configure: error: no acceptable cc found in $PATH
If you got above error Please Use following command.
[root@kapil-pc siege ~]$ yum install gcc*
Than run following command again
[root@kapil-pc siege ~]$ ./configure
checking for a BSD-compatible install… /usr/bin/install -c
checking whether build environment is sane… yes
checking for gawk… gawk
checking whether make sets $(MAKE)… yes
checking build system type… i686-pc-linux-gnu
checking host system type… i686-pc-linux-gnu
checking for style of include used by make… GNU
checking for gcc… gcc
checking for C compiler default output file name… a.out
checking whether the C compiler works… yes
checking whether we are cross compiling… no
checking for suffix of executables…
checking for suffix of object files… o
checking whether we are using the GNU C compiler… yes
checking whether gcc accepts -g… yes
checking for gcc option to accept ANSI C… none needed
checking dependency style of gcc… none
checking how to run the C preprocessor… gcc -E
checking for egrep… grep -E
checking for AIX… no
checking for gcc… (cached) gcc
checking whether we are using the GNU C compiler… (cached) yes
checking whether gcc accepts -g… (cached) yes
checking for gcc option to accept ANSI C… (cached) none needed
checking dependency style of gcc… (cached) none
checking for a sed that does not truncate output… /bin/sed
checking for ld used by gcc… /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld… yes
checking for /usr/bin/ld option to reload object files… -r
checking for BSD-compatible nm… /usr/bin/nm -B
checking whether ln -s works… yes
checking how to recognise dependent libraries… pass_all
checking for ANSI C header files… yes
checking for sys/types.h… yes
checking for sys/stat.h… yes
checking for stdlib.h… yes
checking for string.h… yes
checking for memory.h… yes
checking for strings.h… yes
checking for inttypes.h… yes
checking for stdint.h… yes
checking for unistd.h… yes
checking dlfcn.h usability… yes
checking dlfcn.h presence… yes
checking for dlfcn.h… yes
checking for g++… g++
checking whether we are using the GNU C++ compiler… yes
checking whether g++ accepts -g… yes
checking dependency style of g++… none
checking how to run the C++ preprocessor… g++ -E
checking for g77… no
checking for f77… no
checking for xlf… no
checking for frt… no
checking for pgf77… no
checking for fort77… no
checking for fl32… no
checking for af77… no
checking for f90… no
checking for xlf90… no
checking for pgf90… no
checking for epcf90… no
checking for f95… f95
checking whether we are using the GNU Fortran 77 compiler… yes
checking whether f95 accepts -g… yes
checking the maximum length of command line arguments… 32768
checking command to parse /usr/bin/nm -B output from gcc object… ok
checking for objdir… .libs
checking for ar… ar
checking for ranlib… ranlib
checking for strip… strip
checking if gcc supports -fno-rtti -fno-exceptions… no
checking for gcc option to produce PIC… -fPIC
checking if gcc PIC flag -fPIC works… yes
checking if gcc static flag -static works… yes
checking if gcc supports -c -o file.o… yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries… yes
checking whether -lc should be explicitly linked in… no
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking whether stripping libraries is possible… yes
checking if libtool supports shared libraries… yes
checking whether to build shared libraries… yes
checking whether to build static libraries… yes
configure: creating libtool
appending configuration tag “CXX” to libtool
checking for ld used by g++… /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld… yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries… yes
checking for g++ option to produce PIC… -fPIC
checking if g++ PIC flag -fPIC works… yes
checking if g++ static flag -static works… yes
checking if g++ supports -c -o file.o… yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries… yes
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
appending configuration tag “F77” to libtool
checking if libtool supports shared libraries… yes
checking whether to build shared libraries… yes
checking whether to build static libraries… yes
checking for f95 option to produce PIC… -fPIC
checking if f95 PIC flag -fPIC works… yes
checking if f95 static flag -static works… yes
checking if f95 supports -c -o file.o… yes
checking whether the f95 linker (/usr/bin/ld) supports shared libraries… yes
checking dynamic linker characteristics… GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking for perl… /usr/bin/perl
checking for a POSIX-compliant shell… /bin/sh
checking whether make sets $(MAKE)… (cached) yes
checking for a BSD-compatible install… /usr/bin/install -c
checking for buggy pthread mutex initializers… no
checking for dlopen() in -ldld… no
checking for dlopen() in -ldl… yes
checking for ssl support… yes
checking off/include/openssl/opensslv.h usability… no
checking off/include/openssl/opensslv.h presence… no
checking for off/include/openssl/opensslv.h… no
checking /usr/include/openssl/opensslv.h usability… yes
checking /usr/include/openssl/opensslv.h presence… yes
checking for /usr/include/openssl/opensslv.h… yes
checking for OpenSSL version… >= 0.9.8 (appropriate flag set)
checking for ANSI C header files… (cached) yes
checking for sys/wait.h that is POSIX.1 compatible… yes
checking fcntl.h usability… yes
checking fcntl.h presence… yes
checking for fcntl.h… yes
checking for unistd.h… (cached) yes
checking signal.h usability… yes
checking signal.h presence… yes
checking for signal.h… yes
checking sys/socket.h usability… yes
checking sys/socket.h presence… yes
checking for sys/socket.h… yes
checking sys/select.h usability… yes
checking sys/select.h presence… yes
checking for sys/select.h… yes
checking sys/time.h usability… yes
checking sys/time.h presence… yes
checking for sys/time.h… yes
checking sys/times.h usability… yes
checking sys/times.h presence… yes
checking for sys/times.h… yes
checking sys/resource.h usability… yes
checking sys/resource.h presence… yes
checking for sys/resource.h… yes
checking errno.h usability… yes
checking errno.h presence… yes
checking for errno.h… yes
checking arpa/inet.h usability… yes
checking arpa/inet.h presence… yes
checking for arpa/inet.h… yes
checking netinet/in.h usability… yes
checking netinet/in.h presence… yes
checking for netinet/in.h… yes
checking netdb.h usability… yes
checking netdb.h presence… yes
checking for netdb.h… yes
checking pthread.h usability… yes
checking pthread.h presence… yes
checking for pthread.h… yes
checking for string.h… (cached) yes
checking for strings.h… (cached) yes
checking sched.h usability… yes
checking sched.h presence… yes
checking for sched.h… yes
checking openssl/e_os.h usability… no
checking openssl/e_os.h presence… no
checking for openssl/e_os.h… no
checking openssl/e_os2.h usability… yes
checking openssl/e_os2.h presence… yes
checking for openssl/e_os2.h… yes
checking for an ANSI C-conforming const… yes
checking for size_t… yes
checking whether time.h and sys/time.h may both be included… yes
checking return type of signal handlers… void
checking for working alloca.h… yes
checking for alloca… yes
checking for strchr… yes
checking for memcpy… yes
checking for strncpy… yes
checking for strstr… yes
checking for strlen… yes
checking for strncasecmp… yes
checking for strncmp… yes
checking for socket… yes
checking for gethostbyname… yes
checking for snprintf… yes
checking for strdup… yes
checking for rand_r… yes
checking for localtime_r… yes
checking for getipnodebyname… no
checking for freehostent… no
checking for getopt_long… yes
checking for socket in -lsocket… no
checking for pthread_attr_init in -lpthread… yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating doc/Makefile
config.status: creating html/Makefile
config.status: creating lib/Makefile
config.status: creating lib/joedog/Makefile
config.status: creating include/Makefile
config.status: creating include/joedog/Makefile
config.status: creating utils/Makefile
config.status: creating include/config.h
config.status: executing depfiles commands
config.status: executing default-1 commands
config.status: executing default-2 commands
config.status: executing default-3 commands
config.status: executing default-4 commands
config.status: executing default-5 commands
config.status: executing default-6 commands
——————————————————–
Configuration is complete
Run the following commands to complete the installation:
make
make install
To upgrade an old siegerc file (optional):
mv ~/.siegerc.new ~/.siegerc
For complete documentation: http://www.joedog.org
——————————————————–
[root@kapil-pc siege ~]# make install
Making install in .
make[1]: Entering directory `/home/kapil/testing/siege’
make[2]: Entering directory `/home/kapil/testing/siege’
make[2]: Nothing to be done for `install-exec-am’.
make[2]: Nothing to be done for `install-data-am’.
make[2]: Leaving directory `/home/kapil/testing/siege’
make[1]: Leaving directory `/home/kapil/testing/siege’
Making install in include
make[1]: Entering directory `/home/kapil/testing/siege/include’
Making install in joedog
make[2]: Entering directory `/home/kapil/testing/siege/include/joedog’
make[3]: Entering directory `/home/kapil/testing/siege/include/joedog’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/home/kapil/testing/siege/include/joedog’
make[2]: Leaving directory `/home/kapil/testing/siege/include/joedog’
make[2]: Entering directory `/home/kapil/testing/siege/include’
make[3]: Entering directory `/home/kapil/testing/siege/include’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/home/kapil/testing/siege/include’
make[2]: Leaving directory `/home/kapil/testing/siege/include’
make[1]: Leaving directory `/home/kapil/testing/siege/include’
Making install in lib
make[1]: Entering directory `/home/kapil/testing/siege/lib’
Making install in joedog
make[2]: Entering directory `/home/kapil/testing/siege/lib/joedog’
make[3]: Entering directory `/home/kapil/testing/siege/lib/joedog’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/home/kapil/testing/siege/lib/joedog’
make[2]: Leaving directory `/home/kapil/testing/siege/lib/joedog’
make[2]: Entering directory `/home/kapil/testing/siege/lib’
make[3]: Entering directory `/home/kapil/testing/siege/lib’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/home/kapil/testing/siege/lib’
make[2]: Leaving directory `/home/kapil/testing/siege/lib’
make[1]: Leaving directory `/home/kapil/testing/siege/lib’
Making install in src
make[1]: Entering directory `/home/kapil/testing/siege/src’
make[2]: Entering directory `/home/kapil/testing/siege/src’
test -z “/usr/local/bin” || mkdir -p — “/usr/local/bin”
/bin/sh ../libtool –mode=install /usr/bin/install -c ‘siege’ ‘/usr/local/bin/siege’
/usr/bin/install -c siege /usr/local/bin/siege
make[2]: Nothing to be done for `install-data-am’.
make[2]: Leaving directory `/home/kapil/testing/siege/src’
make[1]: Leaving directory `/home/kapil/testing/siege/src’
Making install in utils
make[1]: Entering directory `/home/kapil/testing/siege/utils’
make[2]: Entering directory `/home/kapil/testing/siege/utils’
make install-exec-hook
make[3]: Entering directory `/home/kapil/testing/siege/utils’
/bin/sh ../utils/mkinstalldirs /usr/local/bin
/bin/sh ../libtool –mode=install /usr/bin/install -c bombardment /usr/local/bin/bombardment
/usr/bin/install -c bombardment /usr/local/bin/bombardment
/bin/sh ../libtool –mode=install /usr/bin/install -c siege2csv.pl /usr/local/bin/siege2csv.pl
/usr/bin/install -c siege2csv.pl /usr/local/bin/siege2csv.pl
/bin/sh ../libtool –mode=install /usr/bin/install -c siege.config /usr/local/bin/siege.config
/usr/bin/install -c siege.config /usr/local/bin/siege.config
make[3]: Leaving directory `/home/kapil/testing/siege/utils’
make[2]: Nothing to be done for `install-data-am’.
make[2]: Leaving directory `/home/kapil/testing/siege/utils’
make[1]: Leaving directory `/home/kapil/testing/siege/utils’
Making install in doc
make[1]: Entering directory `/home/kapil/testing/siege/doc’
make[2]: Entering directory `/home/kapil/testing/siege/doc’
make install-exec-hook
make[3]: Entering directory `/home/kapil/testing/siege/doc’
make[3]: Leaving directory `/home/kapil/testing/siege/doc’
test -z “/usr/local/man/man1” || mkdir -p — “/usr/local/man/man1”
/usr/bin/install -c -m 644 ‘./siege.1’ ‘/usr/local/man/man1/siege.1’
/usr/bin/install -c -m 644 ‘./siege.config.1’ ‘/usr/local/man/man1/siege.config.1’
/usr/bin/install -c -m 644 ‘./bombardment.1’ ‘/usr/local/man/man1/bombardment.1’
/usr/bin/install -c -m 644 ‘./siege2csv.1’ ‘/usr/local/man/man1/siege2csv.1’
test -z “/usr/local/man/man5” || mkdir -p — “/usr/local/man/man5”
/usr/bin/install -c -m 644 ‘./urls_txt.5’ ‘/usr/local/man/man5/urls_txt.5’
test -z “/usr/local/man/man7” || mkdir -p — “/usr/local/man/man7″
/usr/bin/install -c -m 644 ‘./layingsiege.7’ ‘/usr/local/man/man7/layingsiege.7′
make[2]: Leaving directory `/home/kapil/testing/siege/doc’
make[1]: Leaving directory `/home/kapil/testing/siege/doc’
Making install in html
make[1]: Entering directory `/home/kapil/testing/siege/html’
make[2]: Entering directory `/home/kapil/testing/siege/html’
make install-exec-hook
make[3]: Entering directory `/home/kapil/testing/siege/html’
HTML pages not installed
make[3]: Leaving directory `/home/kapil/testing/siege/html’
make[2]: Nothing to be done for `install-data-am’.
make[2]: Leaving directory `/home/kapil/testing/siege/html’
make[1]: Leaving directory `/home/kapil/testing/siege/html’
Now siege installation is done. Than Use following command for using the siege for testing.
[root@kapil-pc siege ~]# siege
SIEGE 2.69
Usage: siege [options]
siege [options] URL
siege -g URL
Options:
-V, –version VERSION, prints version number to screen.
-h, –help HELP, prints this section.
-C, –config CONFIGURATION, show the current configuration.
-v, –verbose VERBOSE, prints notification to screen.
-g, –get GET, pull down headers from the server and display HTTP
transaction. Great for web application debugging.
-c, –concurrent=NUM CONCURRENT users, default is 10
-u, –url=”URL” Deprecated. Set URL as the last argument.
-i, –internet INTERNET user simulation, hits the URLs randomly.
-b, –benchmark BENCHMARK, signifies no delay for time testing.
-t, –time=NUMm TIME based testing where “m” is the modifier S, M, or H
no space between NUM and “m”, ex: –time=1H, one hour test.
-r, –reps=NUM REPS, number of times to run the test, default is 25
-f, –file=FILE FILE, change the configuration file to file.
-R, –rc=FILE RC, change the siegerc file to file. Overrides
the SIEGERC environmental variable.
-l, –log LOG, logs the transaction to PREFIX/var/siege.log
-m, –mark=”text” MARK, mark the log file with a string separator.
-d, –delay=NUM Time DELAY, random delay between 1 and num designed
to simulate human activity. Default value is 3
-H, –header=”text” Add a header to request (can be many)
-A, –user-agent=”text” Sets User-Agent in request
[root@kapil-pc siege ~]#
Google vice president of product management Sundar Pichai told an audience at Computex that the Chrome OS would launch by the fourth quarter.
“When asked about the Chrome vs. Android debate, Mr. Pichai said that providing open source platforms will allow the market to make the best determination about what operating system will work best in the mass market,” TheChromeSource reported.
Google Chrome OS
Announced in November 2009, Chrome OS was designed to be an ultrathin OS, designed with just enough code to push a user online, where the Chrome Web browser could take over. In the meantime, however, Google’s more full-featured Android OS has also fared well, proving to be a popular mobile OS for smartphones and other connected devices.
Google representatives could not be reached for comment by press time.
