How to add mysql system environment variables in Linux
Linux adds mysql system environment variable
After installing mysql yesterday, I added export PATH=/usr/local/ directly in the line above export PATH mysql/bin, and then found that all mysql commands can be used normally, I am very happy.
I was confused the next day. After the Linux system started, I was always logged in. After entering my account and password, I could not log out. After searching on the Internet, I found that the code I added damaged the profile file, causing the system to fail to start. Entering the command line mode can be achieved by pressing ctrl alt F2, and then you can log in successfully after modification.
So I still can’t modify the configuration according to the Windows method, I still need to check it.
When using source code to install software under Linux, you can usually only use the software command in the software installation directory (except for installation using the yum command). This is too troublesome. We hope to use it globally and install the software The path is added to the system environment variables.
There are two ways to add environment variables
//1,使用export命令 export PATH=$PATH:/opt/software/node-v8.9.3-linux-x64/bin/node //export使用方法为 export PATH=$PATH:路径1:路径2:路径n;$PATH为系统变量,表示之前所有设置的路径,如果不加则之前所有的路径都失效。所以必须加上。 //2,修改配置文件/etc/profile vi /etc/profile 在里面加入:export PATH=$PATH:/opt/software/node-v8.9.3-linux-x64/bin/node //如果是修改用户主目录下的.bash_profile,则添加的环境变量只对该用户有效,修改/etc/profile对所有用户都生效。也可以修改/etc/rc.local文件和/root/.bashrc文件。 //修改好配置文件后执行source /etc/profile 或者 source /root/.bashrc使配置文件生效
After correcting the above problem, I found that the connection to mysql was blocked and there was a sock error.
It turns out that mysqlserver is closed, so you need to start mysqlserver.
Give executable permissions chmod x /etc/init.d/mysqld
Add service chkconfig --add mysqld
Display service list chkconfig --list
If you see the mysqld service and 3, 4, and 5 are all "on/open", it will be successful. If it is off/closed, type:
chkconfig --level 345 mysqld on
Modify the mysql environment variable under linux
Find the mysql execution path under linux
eipdb2:~ # cd /eipdb2/mysql/bin/ eipdb2:/eipdb2/mysql/bin # pwd /eipdb2/mysql/bin
Find /etc/profile
Add the environment variable at the end
export PATH=/eipdb2/mysql/bin:$PATH "/etc/profile" 419L, 9839C
source profile to make the environment variable take effect
You can enter it in any directory in the future
mysql -uroot -p password
Login to mysql successfully
The above is the detailed content of How to add mysql system environment variables in Linux. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics









CTEs are a feature introduced by MySQL8.0 to improve the readability and maintenance of complex queries. 1. CTE is a temporary result set, which is only valid in the current query, has a clear structure, and supports duplicate references; 2. Compared with subqueries, CTE is more readable, reusable and supports recursion; 3. Recursive CTE can process hierarchical data, such as organizational structure, which needs to include initial query and recursion parts; 4. Use suggestions include avoiding abuse, naming specifications, paying attention to performance and debugging methods.

MySQL query performance optimization needs to start from the core points, including rational use of indexes, optimization of SQL statements, table structure design and partitioning strategies, and utilization of cache and monitoring tools. 1. Use indexes reasonably: Create indexes on commonly used query fields, avoid full table scanning, pay attention to the combined index order, do not add indexes in low selective fields, and avoid redundant indexes. 2. Optimize SQL queries: Avoid SELECT*, do not use functions in WHERE, reduce subquery nesting, and optimize paging query methods. 3. Table structure design and partitioning: select paradigm or anti-paradigm according to read and write scenarios, select appropriate field types, clean data regularly, and consider horizontal tables to divide tables or partition by time. 4. Utilize cache and monitoring: Use Redis cache to reduce database pressure and enable slow query

MySQL's EXPLAIN is a tool used to analyze query execution plans. You can view the execution process by adding EXPLAIN before the SELECT query. 1. The main fields include id, select_type, table, type, key, Extra, etc.; 2. Efficient query needs to pay attention to type (such as const, eq_ref is the best), key (whether to use the appropriate index) and Extra (avoid Usingfilesort and Usingtemporary); 3. Common optimization suggestions: avoid using functions or blurring the leading wildcards for fields, ensure the consistent field types, reasonably set the connection field index, optimize sorting and grouping operations to improve performance and reduce capital

The aggregation function is used to perform calculations on a set of values and return a single value. Common ones include COUNT, SUM, AVG, MAX, and MIN; GROUPBY groups data by one or more columns and applies an aggregation function to each group. For example, GROUPBYuser_id is required to count the total order amount of each user; SELECTuser_id, SUM(amount)FROMordersGROUPBYuser_id; non-aggregated fields must appear in GROUPBY; multiple fields can be used for multi-condition grouping; HAVING is used instead of WHERE after grouping; application scenarios such as counting the number of classified products, maximum ordering users, monthly sales trends, etc. Mastering these can effectively solve the number

The security of remote access to MySQL can be guaranteed by restricting permissions, encrypting communications, and regular audits. 1. Set a strong password and enable SSL encryption. Force-ssl-mode=REQUIRED when connecting to the client; 2. Restrict access to IP and user rights, create a dedicated account and grant the minimum necessary permissions, and disable root remote login; 3. Configure firewall rules, close unnecessary ports, and use springboard machines or SSH tunnels to enhance access control; 4. Enable logging and regularly audit connection behavior, use monitoring tools to detect abnormal activities in a timely manner to ensure database security.

WhensettingupMySQLtables,choosingtherightdatatypesiscrucialforefficiencyandscalability.1)Understandthedataeachcolumnwillstore—numbers,text,dates,orflags—andchooseaccordingly.2)UseCHARforfixed-lengthdatalikecountrycodesandVARCHARforvariable-lengthdata

Temporary tables are tables with limited scope, and memory tables are tables with different storage methods. Temporary tables are visible in the current session and are automatically deleted after the connection is disconnected. Various storage engines can be used, which are suitable for saving intermediate results and avoiding repeated calculations; 1. Temporary tables support indexing, and multiple sessions can create tables with the same name without affecting each other; 2. The memory table uses the MEMORY engine, and the data is stored in memory, and the restart is lost, which is suitable for cache small data sets with high frequency access; 3. The memory table supports hash indexing, and does not support BLOB and TEXT types, so you need to pay attention to memory usage; 4. The life cycle of the temporary table is limited to the current session, and the memory table is shared by all connections. When choosing, it should be decided based on whether the data is private, whether high-speed access is required and whether it can tolerate loss.

CTE is a temporary result set in MySQL used to simplify complex queries. It can be referenced multiple times in the current query, improving code readability and maintenance. For example, when looking for the latest orders for each user in the orders table, you can first obtain the latest order date for each user through the CTE, and then associate it with the original table to obtain the complete record. Compared with subqueries, the CTE structure is clearer and the logic is easier to debug. Usage tips include explicit alias, concatenating multiple CTEs, and processing tree data with recursive CTEs. Mastering CTE can make SQL more elegant and efficient.
