(p.s sorry for the low quality videos going to use something else for recording <3)

$part 1

https://www.youtube.com/watch?v=ewwoq1ZUo-Y&feature=youtu.be

-> So, login to your server via ssh and let’s start CSF installation by retrieving the package files using wget command:

# wget http://configserver.com/free/csf.tgz

Unpack the archive:

# tar xfz csf.tgz

Navigate to the uncomperssed csf directory:

# cd csf

Run the installer:

# sh install.sh

It will create configuration file and add all required cPanel services to allow list. Let’s disable testing mode by editing main CSF configuration file. Open the file using any editor (vi, nano, etc):

# nano /etc/csf/csf.conf

and change

TESTING = “1?

to

TESTING = “0?

When done, restart CSF:

# csf -r

Now CSF is installed and ready. You can simply manage it via cPanel WHM interface WHM > Config Security & Firewall:    

you have to play with  g_mapConfigs and  g_mapScriptDirectory and custom commands thx to silent mod guys

example:

i'd like to setup a tj mod via shrubbot:

[command]
command  = tj
exec     = set lua_modules "nextmap.lua autopromo.lua TJmod.lua adrenaline.lua" ; set g_mapConfigs "tj_cfg"; restart;
desc     = ^7!^3tj^7 - turn ^3TRICKJUMP MODE ^1on
syntax   =
levels   = 11

[command]
command  = tjoff
exec     = set lua_modules "nextmap.lua autopromo.lua" ; set g_mapConfigs "mapconfigs"; restart;
desc     = ^7!^3tjoff^7 - turn ^3TRICKJUMP MODE ^1off
syntax   =
levels   = 11

well, do NOT set lua modules via your server.cfg, and you can find the above lua modules searching via google

it's just a sample, have fun

cd /usr/local/src/
wget http://www.rfxn.com/downloads/maldetect-current.tar.gz
tar -xzf maldetect-current.tar.gz
cd maldetect-*
sh ./install.sh or sudo sh ./install.sh
maldet --update-ver
maldet --update[/i]

To scan a folder, for example /home you should type maldet -a /home.

Thank you for reading !

██ HostDens.com : Enjoy Unlimited Web Hosting | Beyond Your Expectation
    ██ Reseller Hosting | VPS Servers (Linux) | Shared Hosting
    ██ $1 Hosting | Affordable Shared Web Hosting Services​

<?php
    mysql_connect(‘db_host’, ‘db_username’, ‘password’) or die(‘Could not connect the database : Username or password incorrect’);
    mysql_select_db(‘db_name’) or die (‘No database found’);
    echo ‘Database Connected successfully';
    ?>

It’s very simple concept, first the “mysql_connect” argument will check the database hostname, username and password. If the first argument is true, then PHP take the second line to execute else the script will die with an output given in the Die section. Similarly, mysql_select_db check the database on the server. If both of the arguments are true then you will get an output given after the echo command.

Example:

1, If all of the input data(db_name, username, password, hostname) are right, then the output is like;

    Database Connected successfully

2, If any of the entry in ‘mysql_connect’ section is wrong, then the output is;

   

Could not connect the database : Username or password incorrect

3, If the database entry is wrong;

   

No database found

Thank you for reading !!!

██ HostDens.com : Enjoy Unlimited Web Hosting | Beyond Your Expectation
██ Reseller Hosting| VPS Servers (Windows, Linux) | Shared Hosting
██ $1 Hosting | Affordable Shared Web Hosting Services

Setting up mysql-server-core-5.5 (5.5.30-1~dotdeb.0) …
Setting up mysql-server-5.5 (5.5.30-1~dotdeb.0) …
Installing new version of config file /etc/mysql/debian-start …
Installing new version of config file /etc/init.d/mysql …
Installing new version of config file /etc/logrotate.d/mysql-server …
Stopping MySQL database server: mysqld.
Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
invoke-rc.d: initscript mysql, action “start” failed.
dpkg: error processing mysql-server-5.5 (–configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mysql-server:
mysql-server depends on mysql-server-5.5; however:
Package mysql-server-5.5 is not configured yet.
dpkg: error processing mysql-server (–configure):
dependency problems – leaving unconfigured
configured to not write apport reports
configured to not write apport reports
Errors were encountered while processing:
mysql-server-5.5
mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1) 

Steps to resolve the issue while upgrading MySQL Server:

Take a look at /var/log/syslog and check what errors are you getting:

Quick fix for the below errors:

Error 1:  [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' instead.

Correct syntax for slow queries log in MySQL 5.5:

slow_query_log_file = /your/path/slowqueries.log

Error 2: [Warning] ignore-builtin-innodb is deprecated and will be removed in future releases.

http://dev.mysql.com/doc/innodb/1.1/en/glossary.html#glos_built_in

 

The built-in InnoDB storage engine within MySQL is the original form of distribution for the storage engine. Contrast with the InnoDB Plugin. Starting with MySQL 5.5, the InnoDB Plugin is merged back into the MySQL code base as the built-in InnoDB storage engine (known as InnoDB 1.1).

This distinction is important mainly in MySQL 5.1, where a feature or bug fix might apply to the InnoDB Plugin but not the built-in InnoDB, or vice versa.

See Also InnoDB, plugin.

Simply remove this line if you have in your my.cnf

ignore_builtin_innodb

Error 3: [ERROR] Couldn't load plugin named 'innodb' with soname 'ha_innodb_plugin.so'.

Remove below line from your old my.cnf

plugin-load=innodb=ha_innodb_plugin.so 

Error 4: /usr/sbin/mysqld: unknown variable 'default-character-set=utf8'

Use charset_name as the default character set. This option is deprecated in favor of --character-set-server. See Section 9.5, “Character Set Configuration”. --default-character-set was removed in MySQL 5.5.3. 

http://dev.mysql.com/doc/refman/5.5/en/server-options.html#option_mysqld_default-character-set

Error 5: If you are getting permissions errors you can always start MySQL Server using this:

/usr/sbin/mysqld --skip-grant & 

Don't panic if your MySQL server doesn't start after upgrade. Just keep checking logs and see where is the issue and try to resolve it. Took me a few minutes to figure the issue out but logs are your best friend during upgrade.

Note: Never forget to take back ups before upgrade.

set d1 "set g_gametype 2 ; map sw_oasis_b3 ; set nextmap vstr d2"
set d2 "set g_gametype 2 ; map mlb_daybreak ; set nextmap vstr d3"
set d3 "set g_gametype 2 ; map supplydepot2 ; set nextmap vstr d4"
set d4 "set g_gametype 2 ; map mlb_temple; set nextmap vstr d5"
set d5 "set g_gametype 2 ; map baserace; set nextmap vstr d6"
set d6 "set g_gametype 2 ; map et_mor2_night_final; set nextmap vstr d7"
set d7 "set g_gametype 2 ; map venice_ne4; set nextmap vstr d8"
set d8 "set g_gametype 2 ; map fueldump; set nextmap vstr d9"
set d9 "set g_gametype 2 ; map UJE_00 ; set nextmap vstr d10"
set d10 "set g_gametype 2 ; map goldrush ; set nextmap vstr d1"
vstr d1

Stopwatch Rotation:

// WATCHDOG
set com_watchdog_cmd "vstr m1r1 ; say watchdog found no map running - restarted mapcycle"
// MAP
set m1r1 "g_gametype 3; map oasis; set nextmap vstr m1r2"
set m1r2 "map_restart 0; set nextmap vstr m2r1"
set m2r1 "g_gametype 3; map goldrush; set nextmap vstr m2r2"
set m2r2 "map_restart 0; set nextmap vstr m3r1"
set m3r1 "g_gametype 3; map radar; set nextmap vstr m3r2"
set m3r2 "map_restart 0; set nextmap vstr m4r1"
set m4r1 "g_gametype 3; map railgun; set nextmap vstr m4r2"
set m4r2 "map_restart 0; set nextmap vstr m5r1"
set m5r1 "g_gametype 3; map supplydepot; set nextmap vstr m5r2"
set m5r2 "map_restart 0; set nextmap vstr m6r1"
set m6r1 "g_gametype 3; map caen; set nextmap vstr m6r2"
set m6r2 "map_restart 0; set nextmap vstr m1r1"
vstr m1r1

m1r1 and so on are known as a string library, kind of like a name given to a string of commands - tell the game to run the 'name' and it runs the string of commands associated with it. What basically happens here is the engine stores these lines kind of like "m1r1 command means: set g_gametype to 3, load map oasis and set 'nextmap' to run 'm1r2'". The very last line of the rotation is "vstr m1r1", which tells the engine to actually execute the line m1r1, which will startup the map rotation.

Hence:

g_gametype is set to 3, Oasis is loaded, and once the round of Oasis is finished, it runs "nextmap" which has been set to run m1r2, whereupon the map is restarted the the map cycle continues.

Campaign rotation:

For a campaign rotation, it is fairly similar up to this point. Here is an example of a roation that runs both of the official campaigns, one after the other:

// CAMPAIGN ROTATION - official campaigns
// WATCHDOG
set com_watchdog_cmd "vstr d_initial ; say watchdog found no map running - restarted mapcycle"
// MAP
set d1 "campaign cmpgn_northafrica ; set nextcampaign vstr d2"
set d2 "campaign cmpgn_centraleurope ; set nextcampaign vstr d1"
set d_initial "set g_gametype 4 ; map oasis ; set nextcampaign vstr d2"
vstr d_initial
// END CAMPAIGN ROTATION

Notice the similarity with the stopwatch rotation - really its almost exactly the same. The important things to notice is that: g_gametype is 4, and the campaign mode version of nextmap is "nextcampaign". Secondly, also notice the first campaign being loaded is northafrica, which starts with Oasis, and in the d_initial line the map there (which is first loaded) is also Oasis.

1 = devastating db write performance

"If the value of innodb_flush_log_at_trx_commit is 0, the log buffer is written out to the log file once per second and the flush to disk operation is performed on the log file, but nothing is done at a transaction commit."

"The default value of 1 is the value required for ACID compliance."

If data lost of last one second is not of that much concern then user value 0 or use value 2. InnoDB can be run in a mode where it has lower reliability but in some cases higher performance. Setting innodb_flush_log_at_trx_commit to 0 switches to a mode where transactions are not committed to disk before control is returned to the caller. Instead, disk flushes happens on a timer.

Run a SHOW VARIABLES LIKE 'innodb_flush_log_at_trx_commit' query to get the current value.

2. innodb_buffer_pool_size 70-80% of memory is a safe bet. I set it to 6GB on 8GB box if you are only running website/forums and not game servers.

3. innodb_log_file_size – This depends on your recovery speed needs but 256M seems to be a good balance between reasonable recovery time and good performance

4. innodb_log_buffer_size=4M 4M is good for most cases unless you’re piping large blobs to Innodb in this case increase it a bit.

5. innodb_thread_concurrency=8 Even with current Innodb Scalability Fixes having limited concurrency helps. The actual number may be higher or lower depending on your application and default which is 8 is decent start.

6. innodb_flush_method=O_DIRECT Avoid double buffering and reduce swap pressure, in most cases this setting improves performance. Though be careful if you do not have battery backed up RAID cache as when write IO may suffer.

7. innodb_file_per_table – If you do not have too many tables use this option, so you will not have uncontrolled innodb main tablespace growth which you can’t reclaim. This option was added in MySQL 4.1 and now stable enough to use.

8. Also check if your application can run in READ-COMMITED isolation mode – if it does – set it to be default as transaction-isolation=READ-COMMITTED. This option has some performance benefits, especially in locking in 5.0 and even more to come with MySQL 5.1 and row level replication.

Note: Don't ever convert DB to Innodb engine. It will kill the performance. There are reasons why MySQL comes with MyISAM, InnoDB and Heap engine.

Only use Innodb for the tables having too many inserts/deletes.

Innodb = Row Level Locking

MyISAM = Table Level Locking

Heap = Good for session.

InnoDB is the default storage engine for MySQL as of MySQL 5.5

Few notes:

1. InnoDB doesn't support full-text searches. You can use 3rd party search app for it. sphinx can be good solution.

2. InnoDB will be more I/O bound. Make sure you have good RAID system set up if you have more then 300-500 QPS.

3. MyISAM uses table-level locking on updates and deletes to any existing row, with an option to append new rows instead of taking a lock and inserting them into free space. InnoDB uses row-level locking. For large database applications where many rows are often updated, row-level locking is crucial because a single table-level lock significantly reduces concurrency in the database.

4. MyISAM relies on the filesystem block cache for caching reads to the data rows and indexes, while InnoDB does this within the engine itself, combining the row caches with the index caches.

2. Don't use DISTINCT when you have or could use GROUP BY

3. Don't use ORDER BY RAND() if you have > ~2K records

4. Use SQL_NO_CACHE when you are selecting frequently updated data or large sets of data

5. Avoid wildcards at the start of LIKE queries. It kills the performance on large size of DB.

6. Avoid correlated subqueries and in select and where clause (try to avoid in)

7. No calculated comparisons -- isolate indexed columns

8. ORDER BY and LIMIT work best with equalities and covered indexes

9. Separate text/blobs from metadata, don't put text/blobs in results if you don't need them

10. Derived tables (subqueries in the FROM clause) can be useful for retrieving BLOBs without sorting them. (Self-join can speed up a query if 1st part finds the IDs and uses then to fetch the rest)

11. Know when to split a complex query and join smaller ones

12. Delete small data at a time if you can to avoid table locks.

13. Make similar queries consistent so cache is used

14. Have good SQL query standards

15. Turning OR on multiple index fields (<5.0) into UNION may speed things up (with LIMIT), after 5.0 the index_merge should pick stuff up.

16. Don't use COUNT * on Innodb tables for every search, do it a few times and/or summary tables, or if you need it for the total # of rows, use SQL_CALC_FOUND_ROWS and SELECT FOUND_ROWS()

17. Avoid using IN(...) when selecting on indexed fields, It will kill the performance of SELECT query.

18. Use stored procedures to avoid bandwidth wastage.