Support
FAQ

FAQ - Frequently Asked Questions

1.0 Who, what, where, when, etc.
1.1 What is UpNIX
1.2 Where is UpNIX Located
1.3 When did UpNIX start
1.4 Why should I use UpNIX
1.5 Who uses UpNIX

2.0 Technical Terms
2.1 What is..
2.1.1 OpenBSD
2.1.2 Apache
2.1.3 MySQL
2.1.4 SSL
2.1.5 Shared SSL
2.1.6 Trust Commerce
2.1.7 UNIX
2.1.8 PHP
2.1.9 Perl
2.1.10 SSH
2.1.11 Shell
2.1.12 Shared Server
2.1.13 Static IP Address
2.1.14 SSI

3.0 Technical Questions
3.1 What kind of servers are you using^*
3.2 Why OpenBSD^*
3.3 What about bandwidth
3.4 Your server uptimes suck. Why are they so low^*

4.0 Pre-Customer Questions
.1 Can I get anonymous FTP
.2 What's the deal with your Control Panel
.3 I want to run BNC!^*
.4 What VHosts do you have for IRC^*
.5 What about an IRC Bot^*

1.0 General

1.1 What is UpNIX / What does UpNIX do
UpNIX is a privately held internet services company based in Alberta, Canada. Since 1999, our company has provided businesses worldwide with reliable, professional-class network environments to host shells, email, E-Commerce sites and dynamic applications. We are a group of friendly, dedicated and knowledgeable system administrators looking only to impress through service and performance.

1.2 Where is UpNIX located
Edmonton/Calgary, Alberta, Canada.

1.3 When did UpNIX start
The summer of 1999.

1.4 Why should I use UpNIX
All sorts of reasons. Some of which you'll probably hear at every other hosting site, some of which you won't. You'll have to figure out who you'll believe.

Dedicated Administrators
UpNIX administrators do what they do because they enjoy it. This makes for a good chance not only that an administrator will be around a computer connected to UpNIX 24/7, but that there will be someone willing to go out of their way to make sure all the UpNIX machines are running at their peak.

Administrative technique
UpNIX does something that is unique in the hosting market. We have numerous servers; each server has a single experienced administrator whose sole responsibility it is to look after their set of servers. This creates pride in work, accountability and prevents communication problems that can occur if you have multiple administrators working on one machine. This also creates a better customer experience. A customer can have one point of contact, and often the administrator will get to know clients. (Of course clients can still contact a main Support Desk if their administrator is unavailable)

1.5 Who uses UpNIX
A few notable clients (who've agreed to be listed):
CatSnip - A PHP/MySQL driven site that allows businesses to have their webpage reviewed by users.
MassageAmerica.com - PHP/PostgreSQL driven site that lets New York companies and their employees book massage time. -Very- busy around 10AM (MST). Massage America relies on UpNIX to keep their main source of income running smoothly, fast and securely.

2.0 Technical Terms
2.1 What is..

2.1.1 OpenBSD
A *BSD operating system that powers UpNIX along with thousands of other mission-critical servers reliably and securely 24/7.
OpenBSD

2.1.2 Apache
The world's most popular webserver. A webserver is what displays your website for other people to see.
Apache

2.1.3 MySQL
Probably the most popular Open Source database. Works great for dynamic websites that need to store and retrieve data quickly
MySQL

2.1.4 SSL
Stands for Secure Socket Layer. It is used for secure transactions over the internet.

2.1.5 Shared SSL
To use SSL you need what's called a certificate. And to have a certificate that's signed by someone your browser will recognize you need to pay a good deal of money. What shared SSL does is uses a shared certificate that you, and several other people will use to make secure transactions. The disadvantage to this is that you cannot use your own webaddress to do this, however your transactions are just as secure as they would be with their own certificate.

2.1.6 Trust Commerce
A company that allows webdevelopers to make secure credit card transactions by both providing the interface to do so, and processing them.
TrustCommerce

2.1.7 UNIX
A type of operating system that's known for its power and stability.

2.1.8 PHP
A scripting language used to create dynamic webpages.
PHP

2.1.9 Perl
Another scripting language that can be used to create dynamic webpages. Perl however can do many other things if you have access to a UNIX shell.
Perl

2.1.10 SSH
Stands for Secure SHell. Can be used rather than telnet. Encrypts traffic so that it cannot be sniffed. Usually used only if you have a shell account.

2.1.11 Shell
Could strictly a UNIX term. If you have a shell, that means you've got an account on a UNIX machine. It is from a shell that you can do all of what you'd do with a UNIX machine. Write programs, Email, use with databases, play games, etc.

2.1.12 Shared Server
Means that you share the same physical hardware with other websites. Ideal for those who don't need, or cannot afford their own managed server.

2.1.13 Static IP Address
This means you have access to your own IP Address. Basically an address on the internet people can use to find you with. If you have a static IP, it allows you to run your own servers.

2.1.14 SSI
Stands for Server-Side Includes. Allows you to add minimal functionality to your website easily.

3.1 What kind of machines are you using?^*
2x
850 MHz PIII
L440GX+ Motherboard
512 Megs ECC RAM
2 Fujitsu 10k SCSI Drives (9 and 36 gig)
1 Maxtor 60 gig drive
Antec 2U cases

1x
950 MHz Celeron
Epox 3WTM Motherboard
256 Megs RAM
2 Maxtor 15 Gig hard drives
Antec 1U case (21" Deep)

1x
2600+ XP Athlon
1 Gig DDR RAM
2 IBM 10k SCSI Drives (U160)

These are our public servers, UpNIX also manages a number of dedicated servers for clients.

3.2 Why OpenBSD^*
What UpNIX does is host webpages, and more importantly shells. When you let a bunch of users run around on your system, you need a system that can be reliable and secure under the heaviest of loads. Through direct experience, and hearing stories from others, OpenBSD is the OS to use. Two goals of the OpenBSD project are to be secure and correct (in the BSD sense). Not only does this mean that the source of OpenBSD has been carefully audited, but that much thought has been put into its layout. This results in (obviously) a very secure OS and incredible stability. Albeit OpenBSD may not be one of the fastest BSD's out there, we've put a great deal of effort into optimizing our install of OpenBSD creating what is considered to be the best multi-user platform around.

3.3 Why RedHat ES^*
Before we used RedHat for web hosting, we used OpenBSD for everything, and this worked out we near perfect. However, there were two problems.

One was that the upgrade cycle for OpenBSD was about a year. As we grew, this made for a more difficult upgrade each year.

Second problem was the lack of user control panel. While there are some drawbacks to using one, the simple fact is having administrators make changes for their users doesn't scale well.

RedHat ES solves both these problems as the upgrade cycle is quite long and there are a number of control panels available.

3.4 What about bandwidth^*
UpNIX keeps their servers in 2 different places. Tera-Byte in Edmoton Alberta and Rackspace in Dulles, Virginia.

Tera-Byte is multi-homed through a number providers with connections up to gigbit speeds.

Rackspace is multi-homed through nine different providers, all of which go to a network that is, in their own words, zero downtime. Link speeds range from OC-12 to gigait speed. Needless to say bandwidth speed or quality will never be an issue.

3.5 Your server uptimes suck. Why are they so low^*
Uptimes (days, not percentage) usually range in the 50 day mark for UpNIX servers. The sole reason for this is kernel patches. A kernel patch is usually a security or bugfix released by the operating system vendor which require a server restart. None of UpNIX's servers have stability issues, and all reboots are due to kernel patches or upgrades.

When you run a server that houses so many different users, it's flat out irresponsible to go without patching security holes. So how other hosting companies can go much longer without patching, I'm unsure.

4.0 Pre-Customer Questions

4.1 Can I get anonymous FTP
Anonymous FTP is available only if you have your own IP Address.

4.2 I want to run BNC!^*
No. There's too much room for abuse.

4.3 What VHosts do you have for IRC^*
UpNIX shells aren't really intended for IRC junkies. There's nothing stopping you from firing up BitchX (it's installed infact), but UpNIX prefers to host a developer than someone looking to idle on IRC. So, you can use whatever domain you brought with you for IRC, but we certainly don't supply you with any.

4.4 What about an IRC Bot^*
Those are mostly ok. We need to be told what the IRC channel (and network) the bot is on, and what kind of bot it is. At which point it is decided whether or not it'll be allowed. In addition, there are CPU limits in place that'll kill an overactive bot. Sounds pretty crappy? Better than having your friendly quote spouting bot slowed down cause your shell buddy has a channel protection bot on #Wareznet