#Basics snipped for brevity....


   RewriteEngine on
   #RewriteBase /
   RewriteCond %{REQUEST_FILENAME} !-f
   RewriteCond %{REQUEST_FILENAME} !-d
   RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]


RedirectPermanent / https://www.foo.com/

How come I feel there was a lot of time wasted?!

Here are the readings from the UPS. I am disappointed that it is not reporting battery voltage, but at least I am getting % charged.

battery.charge: 100                     Battery charge (percent of full)
battery.charge.low: 28			Remaining battery level when UPS switches to LB (%)
driver.name: powerpanel			Driver name
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyS0	Serial or USB port
driver.version: 2.2.2			Driver version - NUT release
driver.version.internal: 0.23		Internal driver version
input.frequency: 60.3			Input line frequency (Hz)
input.frequency.nominal: 60		Nominal input line frequency (Hz)
input.transfer.high: 145		High voltage transfer point (V)
input.transfer.low: 90			Low voltage transfer point (V)
input.voltage: 123			Input voltage (V)
input.voltage.nominal: 120		Nominal input voltage (V)
output.voltage: 0			Output voltage (V)
output.voltage.nominal: 120		Nominal output voltage (V)
ups.beeper.status: enabled		UPS beeper status
ups.delay.shutdown: 0			Shutdown with delay command (seconds)
ups.delay.start: 45			Wait before (re)starting (seconds)
ups.firmware: 5.100			UPS firmware
ups.load: 46				Load on UPS (percent of full)
ups.mfr: CyberPower			UPS manufacturer
ups.model: OP1500			UPS model
ups.serial: [unknown]			UPS serial number
ups.status: OL				UPS status
ups.temperature: 35.3			UPS temperature (degrees C)

List of raw FTP commands
(Warning: this is a technical document, not necessary for most FTP use.)

Note that commands marked with a * are not implemented in a number of FTP servers.

Common commands

* ABOR – abort a file transfer
* CWD – change working directory
* DELE – delete a remote file
* LIST – list remote files
* MDTM – return the modification time of a file
* MKD – make a remote directory
* NLST – name list of remote directory
* PASS – send password
* PASV – enter passive mode
* PORT – open a data port
* PWD – print working directory
* QUIT – terminate the connection
* RETR – retrieve a remote file
* RMD – remove a remote directory
* RNFR – rename from
* RNTO – rename to
* SITE – site-specific commands
* SIZE – return the size of a file
* STOR – store a file on the remote host
* TYPE – set transfer type
* USER – send username

Less common commands

* ACCT* – send account information
* APPE – append to a remote file
* CDUP – CWD to the parent of the current directory
* HELP – return help on using the server
* MODE – set transfer mode
* NOOP – do nothing
* REIN* – reinitialize the connection
* STAT – return server status
* STOU – store a file uniquely
* STRU – set file transfer structure
* SYST – return system type

ABOR
Syntax: ABOR

Aborts a file transfer currently in progress.

ACCT*
Syntax: ACCT account-info

This command is used to send account information on systems that require it. Typically sent after a PASS command.

ALLO
Syntax: ALLO size [R max-record-size]

Allocates sufficient storage space to receive a file. If the maximum size of a record also needs to be known, that is sent as a second numeric parameter following a space, the capital letter “R”, and another space.

APPE
Syntax: APPE remote-filename

Append data to the end of a file on the remote host. If the file does not already exist, it is created. This command must be preceded by a PORT or PASV command so that the server knows where to receive data from.

CDUP
Syntax: CDUP

Makes the parent of the current directory be the current directory.

CWD
Syntax: CWD remote-directory

Makes the given directory be the current directory on the remote host.

DELE
Syntax: DELE remote-filename

Deletes the given file on the remote host.

HELP
Syntax: HELP [command]

If a command is given, returns help on that command; otherwise, returns general help for the FTP server (usually a list of supported commands).

LIST
Syntax: LIST [remote-filespec]

If remote-filespec refers to a file, sends information about that file. If remote-filespec refers to a directory, sends information about each file in that directory. remote-filespec defaults to the current directory. This command must be preceded by a PORT or PASV command.

MDTM
Syntax: MDTM remote-filename

Returns the last-modified time of the given file on the remote host in the format “YYYYMMDDhhmmss”: YYYY is the four-digit year, MM is the month from 01 to 12, DD is the day of the month from 01 to 31, hh is the hour from 00 to 23, mm is the minute from 00 to 59, and ss is the second from 00 to 59.

MKD
Syntax: MKD remote-directory

Creates the named directory on the remote host.

MODE
Syntax: MODE mode-character

Sets the transfer mode to one of:

* S – Stream
* B – Block
* C – Compressed

The default mode is Stream.

NLST
Syntax: NLST [remote-directory]

Returns a list of filenames in the given directory (defaulting to the current directory), with no other information. Must be preceded by a PORT or PASV command.

NOOP
Syntax: NOOP

Does nothing except return a response.

PASS
Syntax: PASS password

After sending the USER command, send this command to complete the login process. (Note, however, that an ACCT command may have to be used on some systems.)

PASV
Syntax: PASV

Tells the server to enter “passive mode”. In passive mode, the server will wait for the client to establish a connection with it rather than attempting to connect to a client-specified port. The server will respond with the address of the port it is listening on, with a message like:
227 Entering Passive Mode (a1,a2,a3,a4,p1,p2)
where a1.a2.a3.a4 is the IP address and p1*256+p2 is the port number.

PORT
Syntax: PORT a1,a2,a3,a4,p1,p2

Specifies the host and port to which the server should connect for the next file transfer. This is interpreted as IP address a1.a2.a3.a4, port p1*256+p2.

PWD
Syntax: PWD

Returns the name of the current directory on the remote host.

QUIT
Syntax: QUIT

Terminates the command connection.

REIN*
Syntax: REIN

Reinitializes the command connection – cancels the current user/password/account information. Should be followed by a USER command for another login.

REST
Syntax: REST position

Sets the point at which a file transfer should start; useful for resuming interrupted transfers. For nonstructured files, this is simply a decimal number. This command must immediately precede a data transfer command (RETR or STOR only); i.e. it must come after any PORT or PASV command.

RETR
Syntax: RETR remote-filename

Begins transmission of a file from the remote host. Must be preceded by either a PORT command or a PASV command to indicate where the server should send data.

RMD
Syntax: RMD remote-directory

Deletes the named directory on the remote host.

RNFR
Syntax: RNFR from-filename

Used when renaming a file. Use this command to specify the file to be renamed; follow it with an RNTO command to specify the new name for the file.

RNTO
Syntax: RNTO to-filename

Used when renaming a file. After sending an RNFR command to specify the file to rename, send this command to specify the new name for the file.

SITE*
Syntax: SITE site-specific-command

Executes a site-specific command.

SIZE
Syntax: SIZE remote-filename

Returns the size of the remote file as a decimal number.

STAT
Syntax: STAT [remote-filespec]

If invoked without parameters, returns general status information about the FTP server process. If a parameter is given, acts like the LIST command, except that data is sent over the control connection (no PORT or PASV command is required).

STOR
Syntax: STOR remote-filename

Begins transmission of a file to the remote site. Must be preceded by either a PORT command or a PASV command so the server knows where to accept data from.

STOU
Syntax: STOU

Begins transmission of a file to the remote site; the remote filename will be unique in the current directory. The response from the server will include the filename.

STRU
Syntax: STRU structure-character

Sets the file structure for transfer to one of:

* F – File (no structure)
* R – Record structure
* P – Page structure

The default structure is File.

SYST
Syntax: SYST

Returns a word identifying the system, the word “Type:”, and the default transfer type (as would be set by the TYPE command). For example: UNIX Type: L8

TYPE
Syntax: TYPE type-character [second-type-character]

Sets the type of file to be transferred. type-character can be any of:

* A – ASCII text
* E – EBCDIC text
* I – image (binary data)
* L – local format

For A and E, the second-type-character specifies how the text should be interpreted. It can be:

* N – Non-print (not destined for printing). This is the default if second-type-character is omitted.
* T – Telnet format control (, , etc.)
* C – ASA Carriage Control

For L, the second-type-character specifies the number of bits per byte on the local system, and may not be omitted.

USER
Syntax: USER username

Send this command to begin the login process. username should be a valid username on the system, or “anonymous” to initiate an anonymous login.

ntp pool clients should see no interruption in services. However, this means that kulish.com will be providing a stratum 2 time source while the gps is offline. **

Stratum 1 services are expected to resume at, or before, 2000 CST.

During maintenance we will be making final adjustments to the GPS system before going “live”.

** A second stratum 1 server will be coming online Q2 2008 to avoid the stratum bump in the future.

NOTE: See comments for details about the outage.

1. WILL NOT answer queries
2. WILL NOT forward queries
3. WILL NOT perform recursion
4. WILL allow transfers from specified slaves

Zone and configuration files are backed up disk to disk via rsync.

Single point editing of our name space.

Single point of failure. If server is lost, updates to DNS cannot be made until another master is brought online.

options {
directory “/etc”;
pid-file “/var/run/named.pid”;
version “Windows 3.11″;
allow-query {“none”; };
allow-recursion {“none”; };
notify yes;
also-notify {
IPn.IPn.IPn.IPn;
};
allow-transfer {
IPn.IPn.IPn.IPn;
};
};

zone “my.hosts.net” {
type master;
file “/etc/my.hosts.net”;
};

We’re using the postfix+amavis+clamd+spamassassin setup.

While we’ve been doing without it for a few months (using client side stuff until I found time), I still don’t remember it working this well on the last server install.

Here’s a wopper of an email, just after the installation and testing were completed. The receiving parties and server names have been sanitized to protect the marginally innocent (**PROTECTED**).

From ***PRO@TECTED***.com Tue Feb 14 23:02:47 2006
Return-Path:
Delivered-To: spam-quarantine
X-Envelope-From:
X-Envelope-To: **PROTECTED**
X-Quarantine-Id:
Received: from lh (unknown [61.130.156.43])
by **PROTECTED** (Postfix) with SMTP id D90164B92A;
Tue, 14 Feb 2006 23:02:35 -0600 (CST)
Received: from 61.130.156.43 (HELO localhost.localdomain) (61.130.156.43)
by 61.130.156.43 with SMTP; Wed, 15 Feb 2006 07:06:05 +0200
Message-Id:

#!/usr/bin/perl -w

use strict;

# Backup – Script used to backup MySQL databases to an NFS share.
# VERSION: 1.2
# DATE: 12152005
# AUTHOR: packetmad

# This is a Freebsd 4.x-centric script. It may run on other
# versions of Freebsd, or any other BSD for that matter, but I
# wrote it on a Freebsd 4.7 system. It’s not even guaranteed
# to run on that.

# Speaking of guarantees, warranties, etc., there ain’t one, so
# don’t even try. :P
# I am not responsible for the output of this script, nor am I
# responsible for any damage or data loss as a result of using
# this script. In short, I am not responsible for anything
# regarding this script.
# Furthermore, I am not responsible if this script causes
# Your dog to die, your wife to leave you, or
# your truck to break down.
# I am releasing this script under the conventions of the BSD
# license. You can use it, modify it, sleep with it, or
# whatever. If you do find this script useful or have
# suggestions on a better way to do some things contained here
# in, I welcome all correspondence.
# The latest version of this script can be obtained at:
# http://tech.kulish.com

# USE THIS SCRIPT AT YOUR OWN RISK!!!!!!!!!!!!!!!!!!

# Change Log
# v1.1
# Date: 11302002
# Initial Release, absolutely BUG FREE! :)
# v1.2
# Date: 12152005
# Added compression functionality
# Added naming of backup files by date
# Changed longterm storeage directory for 1back to store1

###
# Declare variables and arrays.
###

my (
$bdir, $sysname, $logfile, %databases, $key, $database, $rightnow
);

$bdir = ‘/databases/’;
chomp ( $sysname = `uname -n` );
chomp ( $rightnow = `date +%m%d%G%H%M` );
#print $rightnow;
# Databases we want to backup and associated archive names.
# Database => sql file pairs.

%databases = (‘testdb1′ => ‘testdb1.sql’,
‘testdb2′ => ‘testdb2.sql’);

###
# Backup Section
###
foreach $key (sort keys %databases) {
$database = $databases{$key};
`mysqldump -uUSERNAME -pPASSWORD $key >> $bdir$sysname/$database`;}

###
# Compression Functionality
###

foreach $key (sort keys %databases) {
$database = $databases{$key};
`gzip -c $bdir$sysname/$database > $bdir$sysname/$rightnow$database.gz`;}

# scp them to the fileshare
#`scp $bdir$sysname/*.gz USERNAME\@SERVER:databases`;

###
# Clean backup dir
###

`rm -rf $bdir$sysname/*.sql`;
`mv $bdir$sysname/*.gz $bdir$sysname/store1`;

I clustered 4 Pentium 133s running FreeBSD 5.1-Release using LAM-MPI for the messaging interface and Ganglia for the monitoring. You can view the statistics here, but you must be registered and signed-in to do so (the pages are fairly graphic intensive).

I believe there will be a clustering How-To posted to BSDHound.com in the future, and if it is, I will be sure to post and update here.

Keep in mind, you must have the proper settings active in your kernel for this to work.

Here it is:

#!/usr/bin/perl -w

use strict;

# If no arguments are given, print a brief help message
if (!defined($ARGV[0]))
{
print “\n”;
print “Help:\n”;
print “Lexar Jumpdrive mounting script\n”;
print “\n”;
print “You must provide one of the following arguments:\n”;
print “m Mounts the Jumpdrive.\n”;
print “u UnMounts the Jumpdrive.\n”;
print “\n”;
print “Example: lexar m\n”;
print “\n”;
}

# m mounts the jumpdrive
elsif ($ARGV[0] eq “m”)
{
# mounting the jumpdrive at /lexar
# this can be set to whatever you like
system “/sbin/mount -t msdos /dev/da0s1 /lexar”;
print “Jumpdrive mounted at /lexar.\n”;
}

elsif ($ARGV[0] eq “u”)
{
# umounts the jumpdrive
system “/sbin/umount /lexar”;
print “Jumpdrive unmounted.\n”;
}

I use alot of opensource and I try to avoid doing that to others (usually successful), as well as avoiding the “the distro I use is better, so you should just switch to fix your problem” answers. There is definately reason to read the documentation, but at some point its just proper to be upstanding and state “such and such should fix your problem, when you’re back up and running make sure to look at the manpage”. Their normal excuse is “I’m sick of answering all these newbie questions that are in the clearly addressed manpages”. To that I say, THEN GET OUT OF ?N*X SUPPORT CHANNELS.

Anyway, I digress. Now to the real problem, me blowing up my /etc/fstab and how to fix it, in case it happens to you!

I started a forum thread entitled “Opensource Attitudes” to address the rant portion of this. If anyone has any questions about the technical side of this article, feel free to start a thread in the appropriate forum.

So the faulty decision I made was to add a USB jumpdrive to my fstab. I wouldn’t recommend this :)

To fix the ensuing cluster, I did the following:

1. Rebooted into Single User Mode
2. Mount (to see whats mounted and how)
3. cat /etc/fstab (to see what filesystems I normally mount)
4. mount /dev/ad0s2a /usr (to get my utilities, namely vi)
5. mount -u -w / (This mounts / writeable so you can save your new fstab)
6. vi /etc/fstab to remove your bad entry or whatever it is that was changed
7. reboot

At this point everything should be back to where it was before the fateful edit, if not, just repeat the steps above until it is.

It’s also a good idea to make a copy of your /etc/fstab in case it’s fat-fingered yet again. That way, you can at least see the way it was previously broke (better yet, make a backup before your initial edit of the working copy… lesson learned)

Hope this saves some of you from the open-source ego-trip, at least for fixing your file systems.