From http:\/\/www.v-nessa.net\/<\/p>\n
(Sexy g33k chicks rock…)<\/p>\n
I can think of a few things that are wrong with that title but in all seriousness\u2026don\u2019t you ever wonder where cPanel stores the config changes that you make in WHM? Automation is the key nowadays, and lately that\u2019s required me to get a little down and dirty with cPanel to find its deepest secrets. *This information is not official documentation, nor is it backed up by cPanel or set in stone. In other words, don\u2019t blame me if you mess up your server.<\/p>\n
These are files that store the information read and used by WHM (as of 11.23.6)<\/p>\n
* IP addresses: \/etc\/ips
\n * Reserved IPs: \/etc\/reservedips
\n * Reserved IP reasons: \/etc\/reservedipreasons
\n * IP address pool: \/etc\/ipaddrpool
\n * Access hash (WHM remote access key): \/home\/user\/.accesshash or \/root\/.accesshash
\n * cPanel update preferences: \/etc\/cpupdate.conf
\n * Basic cPanel\/WHM setup: \/etc\/wwwacct.conf
\n * System mail preferences: \/etc\/localaliases
\n * Exim open relay list: \/etc\/alwaysrelay
\n * Server-wide max emails per hour: \/var\/cpanel\/maxemailsperhour
\n * Tweak settings: \/var\/cpanel\/cpanel.config
\n * Packages: \/var\/cpanel\/packages\/
\n * Features: \/var\/cpanel\/features\/
\n * User data: \/var\/cpanel\/users\/ and \/var\/cpanel\/userdata
\n * Apache templates: \/var\/cpanel\/templates\/apache(1,2)
\n * Exim config template: \/etc\/exim.conf.localopts
\n * Exim mail IPs: \/etc\/mailips
\n * rDNS for mail ips: \/etc\/mail_reverse_dns
\n * Clustering: \/var\/cpanel\/cluster\/root\/config
\n * Service manager: \/etc\/chkserv.d
\n * Users and their domains: \/etc\/userdomains
\n * Users and their main domains: \/etc\/trueuserdomains
\n * Users and their owners: \/etc\/trueuserowners
\n * Main cPanel IP: \/var\/cpanel\/mainip
\n * cPanel version: \/usr\/local\/cpanel\/version
\n * Resellers: \/var\/cpanel\/resellers
\n * Reseller nameservers: \/var\/cpanel\/resellers-nameservers<\/p>\n
These are a few scripst that you can use to achieve the same results of their WHM equivalents:<\/p>\n
* Initialize quotes: \/scripts\/initquotas Obviously there are a ton more, and just about anything done in WHM can be done directly on the server. The main things to remember:<\/p>\n Scripts are mainly stored in \/scripts and \/usr\/local\/cpanel\/bin<\/p>\n Data files are in \/var\/cpanel<\/p>\n Config files are in \/etc\/ and \/usr\/local\/cpanel<\/user><\/reason><\/user><\/p>\n","protected":false},"excerpt":{"rendered":" From http:\/\/www.v-nessa.net\/ (Sexy g33k chicks rock…) I can think of a few things that are wrong with that title but in all seriousness\u2026don\u2019t you ever wonder where cPanel stores the config changes that you make in WHM? Automation is the key nowadays, and lately that\u2019s required me to get a little down and dirty with… <\/p>\n
\n * Compile Apache: \/scripts\/easyapache (you can pass additional options \u2013 see EasyApache 2 docs)
\n * Update cPanel: \/scripts\/upcp
\n * Enable\/disable tweak settings: \/scripts\/smtpmailgidonly on|off
\n * Change PHP API and suExec settings: \/usr\/local\/cpanel\/bin\/rebuild_phpconf
\n * Suspend an account: \/scripts\/suspendacct
\n * Terminate an account: \/scripts\/killacct