Phat Site Blog

Ubuntu does have eBox,which provides a web interface for monitoring and configuring server systems.Unfortunately, this works only via Firefox (not via w3m or links), which means you’ll have to either install X on your server or allow it to run anhttps server specifically for eBox and access that via a desktop machine.

Personally, I’m not enthusiastic about web-based tools; I’d rather seesomething more along YaST lines that can be run on a console on the machinebeing configured. Ubuntu also has Puppet available, but that’s aboutconfiguration file maintenance rather than about providing any kind of configurationmanagement interface.

Another management tool offered is phpMyAdmin,which allows you to administer your MySQL server via a web interface. As witheverything else, it’s a straightforward install, which will reconfigure Apacheas part of the install and even set up your database automatically. Youcan also do this manually if you prefer. Once Apache is installed, if you’re stickingto a console, use links rather than w3m, as phpmyadmin worksbetter with frames. However, in this case you may want to just stay with theMySQL command line, as phpMyAdmin is definitely more usable in a graphicalbrowser. It is useful if you don’t want to have to remember (or lookup) sets of SQL statements.

Conclusions

It’s convenient to have a server install that’s entirely separate from thedesktop install, and while itmay not be as visually slick as the desktop version, that’s not really whatyou want on a server. The install was straightforward; I really liked thepackage collections; and everything was functional on first bootup. Fiveyears of support is good, and all the software installed was fairly up-to-date(within a couple of release points, which is reasonable given the testingcycle needed for a long-term release). Ubuntu provides security updatesregularly, so any security improvements in more recent releases should berolled out to your servers quickly.

One problem I found was that the documentation available online is a bitshaky. In some cases, it still refers to earlier releases, which isn’tvery reassuring. However, Ubuntu is obviously making an effort with itsdocumentation, and it’s easier to find information than it is with some otherdistros.

Overall, Lucid Lynx is an impressive offering and definitely something I’d be happy touse for my own servers. more console-driven system management tools andbetter documentation, would make it an even better option.

Juliet Kemp has been messing around with Linux systems, for financial reward and otherwise, for about a decade. she is also the author of “Linux System Administration Recipes: A Problem-Solution Approach” (Apress, 2009).

Follow ServerWatch on Twitter

Ubuntu LTS 10.04, a Linux OS at Its Best

I’d like to convert an apache module I’ve written to work
under nginx. can somebody loan me a clue for getting started?

Background
———-

The logic is pretty simple:

1. based on the input URI, determine what file will be
sent. this will possibly involved a (cached) db lookup.

2a. set these headers:

Content-disposition:
ETag:
X-mod_asset-version: (my custom header)

2b. set mime type.

3. allow nginx to send the bytes of the file. Hopefully
it will handle these headers:

Last-Modified:
Content-Length:
Accept-Ranges:
Content-Range:
Content-Length:

Questions
———

For 2b, this is the proper way?

r->headers_out.content_type.len = sizeof(“image/gif”) – 1;
r->headers_out.content_type.data = (u_char *) “image/gif”;

is there a special way to malloc the .data so that it
will be freed automatically when the request is complete?

For 3, should I be using X-Accel-Redirect?

add_header(“X-Accel-Redirect: /protected/iso.img”);

If so, then I can simply set my headers and pass along to the next
phase?

Any simple example modules I can use as a starting point?

Many TIA!!
Mark

–
Mark Harrison
Pixar Animation Studios

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx

Nginx Maillist: quick start on writing a module?

Apache’s West Kalabsha I-1X discovery in the Faghur Basin of Egypt’s Western desert tested at 4554b/d and 10.1mmcf/d, the US-based operator said on 25 March 2010. The well, located 10 miles southwest of the operator’s Phiops field flowed from 105ft of net pay in the Jurassic Safa formation.

The West Kalabsha I-1X is the most recent in a series of oil discoveries in the Faghur Basin. Apache is expanding processing and transportation infrastructure to raise production capacity in the Faghur from 8100b/d to 40,000b/d in late 2010.

“Apache previously established production in the Safa formation at West Kalabsha-C and Phiops in the Faghur Basin,” said Tom Voytovich, VP of Apache’s Egypt Region. “This most recent discovery solidifies the Jurassic Safa as a primary objective in the basin. The well, on a structure identified by 3D seismic, encountered pay in over 200ft of total sand, demonstrating the potential size of Safa accumulations in the Faghur. this discovery certainly adds a new dimension to our exploration focus.

“West Kalabsha is proving to be a fertile hunting ground; with the ongoing infrastructure expansion, the time from concept to actual production should be shortened dramatically,” Voytovich said. The company has two new 3D seismic surveys completed in the basin, and is about to begin acquisition on its largest survey of the year to the west, along the trend established by recent discoveries, in an area where no previous 3D data exists but regional 2D data indicates promising geological features, he added.

Apache owns 100% interest in the West Kalabsha concession and plans to drill four more exploratory wells targeting the Alam el Bueib (AEB) and Safa formations in the Faghur basin this year. Apache plans to drill an appraisal test two miles southwest of the latest discovery before full development plans are formulated.

by: Jennifer Pallanich,jpallanich@offshore-engineer.com

Apache has another Faghur hit

I need to redirect traffic between a few servers on a linux vps hosting cluster using rewrite rules — does anyone know the easiest method to utilize rewrite in apache v2.22?

How do you setup rewrite rules for apache v2.22?

vi /etc/yum.repos.d/CentOS-Base.repo
find [centosplus] and locate:
enabled = 0

change to

enabled = 1

yum install php php-mysql mysql-server php-gd postgres ImageMagick ImageMagick-devel

Now you got php, mysql, graphic manipulation, and posgres installed.

Let’s setup your MySQL:
/etc/init.d/mysqld restart – after you run this, you will get a bunch of useful text, read it!
/usr/bin/mysqladmin -u root password ‘CHANGEMETOHARDPASSWORD’
/sbin/chkconfig mysqld –level 2345 on  – lets mysql startup on reboot

Now you have PHP installed with common libraries such as image manipulation and postgres and mysql for database work.