Do I Need Root Access?

Many operating systems, such as Mac OS X, let administrator accounts, which give greater access while shielding the user from most of the pitfalls of full root access. In some cases, the root account is disabled by default, and must be specially enabled.

Software defects which allow a user to "gain root" (to perform with super user privileges code supplied by that user) are a main security issue, and the fixing of such software is a major part of maintaining a secure system. One common way of gaining root is to cause a buffer overflow in a program already running with super user privileges. This is often subsided in modern operating systems by running critical services, such as httpd, under a unique limited account.

Access Root of Website, Accesses to the Root, Accesses under Root

If a person "has root access", it means that they are able to act as the administrator of that computer. "Having root" (ie, being the administrator of the system) is commonly associated with a so-called "feeling of power", to rule and divide, mostly by less experienced users. Many knowledgeable Unix system administrators observe this as insignificant, with the argument that "it's only meant for maintaining the system". Yet, boasting about having root access is quite common on the Internet.

Root, or getting root, is receiving the privilege to access all of the places on a computer. If you think of a server as a tree the roots control the tree. The roots of a tree allow water in, minerals in and are the lifeblood of the tree. Anything, which goes into the roots, goes into the entire tree. Anything that affects the roots of a tree affects the entire tree.

Servers are set up with a similar thought process in that parts of the server are broken down into different areas. Each different area has its own privileges. One area cannot involve another area. For example, if there are three web sites on a server and one web site breaks the other two will not be affected.

Each web site is in its own part of the server and can involve only itself. Though, there has to be a master account or way into each area or site. If you don’t have a master method to right to use all sites at once it would be a fantastic quantity of effort if something needed to be fixed or updated on every site on the server.

The method or access to all of the parts of the server is б root access.б when someone has root access they can affect everything on the entire server or change everything on the entire server. There are no restrictions with root access. If an error is made in root access it could "wipe out the entire server."

Unless you are leasing your own server and need to have an effect on every account on the server you don’t need root access. There are some things you can do to make your site run more efficient with root access, but unless you know what you are doing you could destroy the entire server. And web-hosting providers are not going to allow that to happen because chances are there is more than one client on the server.