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 still says that service command not found
here is my.cnf file :
# Example MySQL config file for large systems.
# This is for a large system with memory = 512M where the system runs mainly
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /var/lib/mysql) or
# ~/.my.cnf to set user-specific options.
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.
# The following options will be passed to all MySQL clients
#password = your_password
port = 3306
socket = /var/lib/mysql/mysql.sock
# Here follows entries for some specific programs
# The MySQL server
port = 3306
socket = /var/lib/mysql/mysql.sock
key_buffer = 256M
max_allowed_packet = 1M
table_cache = 256
sort_buffer_size = 1M
read_buffer_size = 1M
read_rnd_buffer_size = 4M
myisam_sort_buffer_size = 64M
thread_cache = 8
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 8
# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
# Replication Master Server (default)
# binary logging is required for replication
# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1
# Replication Slave (comment out master section to use this)
# To configure this host as a replication slave, you can choose between
# two methods :
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
# where you replace <host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
# The replication master for this slave - required
#master-host = <hostname>
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
# binary logging - not required for slaves, but recommended
# Point the following paths to different dedicated disks
#tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname
# Uncomment the following if you are using BDB tables
#bdb_cache_size = 64M
#bdb_max_lock = 100000
# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /var/lib/mysql/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /var/lib/mysql/
#innodb_log_arch_dir = /var/lib/mysql/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 256M
#innodb_additional_mem_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 64M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50
# The safe_mysqld script
max_allowed_packet = 16M
# Remove the next comment character if you are not familiar with SQL
OK, I don't see anything in that file that looks blatantly incorrect. It's also really bizarre that you don't have the service command. Can you type "locate service" (no quotes) and then type the full path. Or just do /etc/ec.d/mysqld start (do an ls of the /etc/rc.d directory in vcase the MySQL start up file is named something else like mysql-server -- I've only used MySQL on Red Hat and Debian, so I'm not sure how SuSE sets it up).
I'd also suggest looking at the error log (/var/lib/mysql/mysqld.log per your my.cnf) in case it has any clues of where the problem is originating.
I didn't do it yet
I have more additional questions:
1.mysql rpm does provide server or i need mysql administrator???
2. Do I have problem to use proffesionaly sql from any application in linux???
3.mysql runs only only in terminal mode???
thanks once again for trying to help me
1) If you're running Red hat or a clone, you should have the mysql-server RPM. The fact that a mysqld binary exists suggests you have it installed, but it wouldn't hurt to double check.
2) Sorry, I don't understand your question. MySQL (recent versions) implement most of the ANSI SQL standard and many database driven apps can be configured to talk to MySQL, if that's what you're asking.
3) There is a command line client. There are also graphical front ends. The MySQL daemon is just a database server, which is rather useless unless you have database clients to read/write data to the database. There are several GUI tools (among them phpMyAdmin if you're running a Web server w/ PHP) that can provide a GII for MySQL use and administration.
SuSE has a number or root rc scripts that you use instead of the service command.
Check if the service is running using "sudo /usr/sbin/rcmysql status"
If it responds unused, then start it with "sudo /usr/sbin/rcmysql start"
Go into YaST and enable mysqld to start with the computer if that is what you want to do.
Also, read through the mysql manual at "/usr/share/doc/packages/mysql/manual.pdf". You shouldn't need to run the mysql_install_db if you installed it from the rpm. However the manual has a post installation section that is very important on the things you need to do right away to make the database more secure.
As far as I kow, "rcmysql start" should work in SUSE 10, and "service mysql start" at least also works in SUSE 10.1. Alternatively, you can use YaST (System->Runlevel Editor) to specify the runlevels in which the mysql server will be started automatically.
Edit: I missed the second page of this thread. So I'm only supporting jschiwal, but what does this mean: "I misread who sent btmiller's post, and thought you had SuSE." That's just what mihalisla said in the very first post.
Last edited by spirit receiver; 07-10-2006 at 03:15 AM.