Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
It is extremely beneficial for a systems admin to have at least a working knowledge of the applications that are running on the servers they are administering.
A basic knowledge of things like which port MySQL runs on, how to check that the server is running, how to run simple queries, how to install and secure a MySQL installation are things I'd consider essential when hiring. The same for apache.
Even if companies have "teams" for these it is highly desirable to have a sysadmin that can understand when these teams talk about MySQL master/slave replication, circular replication, or apache name based virtual hosting and IP based virtual hosting.
May be as an Admin,
1. Update new patches
2. Troubleshoot the issues
3. Fine tune the server performance
4. Grant permission to users/clients
5. Manager cluster resources
6. Manage the backup/ restore the backup
7. Logging the slow queries
8. Mainly DB team think about to build database
9. As an Admin need to think about day to day management and High availability of the DB server
Even though "DBAs Are Gods,™" those Gods do need to be able to talk to Mortals who have a vague notion of what they are doing. And also, "one does not wish to bother The Gods for trivial matters." Therefore, to the degree that "day-to-day administration of the platform" logically involves routine activities regarding the databases, or routine diagnosis of problems (say, in TCP/IP connections) as they crop up from time to time, a sysadmin needs to have a fair amount of understanding of this stuff. (Which understanding must also include "knowing where the deep water starts" and having the lack-of-hubris needed to stay out of there.)
Think of it like a car, you don't need to know how to build an engine to drive a car but you should know if it uses petrol or diesel and also where to put these in!
For the americans: he means gas/gasoline.
As a Sysop, I want to know how to administer anything that runs on my machines. Anything that has a config file, log file and init.d startup script is something that I go out of my way to know about for the inevitable day that it breaks.
Mysql can be installed using packages in the cd or we can download the rpm from the website why do we need to do that when we have mysql rpm in the dvd
Originally Posted by James0806
Why companies ask for mysql,oracle sql knowledge when there is a separate team for that and what is the work of system administrator on the databases like mysql and sql
These questions would seem to indicate that you're either a brand-new systems administrator, or you haven't yet got a job as one.
Companies can ASK for whatever they want...if they want you to have a doctorate degree in ancient Greek, you'd better have one. Why? Because they WANT IT, that's why. Some other reasons, which an administrator with experience would point out would be:
Your servers may be running MySQL...shouldn't you be able to troubleshoot the software ON the server?
Managing MySQL may be part of your job.
The DBA 'team' may consist of one person at some companies, and 50 at another...who knows?
Many applications use MySQL as a back end for data, so the DBA's won't be touching it...just the systems administrators.
...which goes to your next question, about why you would install it from a website/repository. If MySQL has 10 updates between when the DVD is released and the time you've installed your new server with it, wouldn't you WANT the latest package???
Let me put it this way.. It's not a system admins job to fix bugs, but it is partially his job to find some of those bugs...
Here's why: A sysadmin doesn't only install stuff, but it makes sure everything works together and when they don't (and trust me, they ussualy don't) it's his job to find out why (and if he can, to fix it -- if he can't, to report it).. You can't debug something without knowing nothing about it..
Here's another example: How will you update your DB server not knowing SQL? Just running the provided scripts? Pff.. Sure, databases and queries never brake :P Hell, a sysadmin will probably know more about the database software than most of the developers..
Last edited by Smokey_justme; 08-07-2014 at 05:44 PM.