11. LAMP server: Linux.
4MLinux uses the LTS Linux kernel. You should keep it (and the whole system) up-to-date by executing the "zk update" command.
Note:
Updates are released monthly (usually on the first weekend of each month).
12. LAMP server: Apache.
Apache web server in 4MLinux has the PHP support enabled by default. Command-line usage: httpd start (stop, restart, test).
Note:
By default, 4MLinux uses stunnel to enable the "https" support for Apache and the "smtps" support for Postfix. Edit the /etc/stunnel/stunnel.conf to change these settings. Go to the /usr/share/stunnel/script directory if you need to generate a self-signed certificate.
13. LAMP server: MySQL.
The 4MLinux Server incorporates the MariaDB database management system. Command-line usage: mysqld start (stop, restart, test). You can use Adminer or Webmin to create/manage your databases.
Note:
Randomly generated MySQL root's password is stored in the .mysql_passwd file located in the root's home directory. Additionally, the password is exported to Webmin, meaning that its admin uses safe (password-protected) MySQL without the need to log in manually.
14. LAMP server: PHP.
The 4MLinux Server includes both PHP5 and PHP7 (see the note below). Additionally, the ionCube Loader is enabled by default.
Note:
Open your terminal and execute the php7 command to disable PHP5 and to enable PHP7. And vice versa: execute the php5 command to disable PHP7 and to enable PHP5.
15. Other servers: SSH.
The SSH daemon in 4MLinux (OpenSSH) has the SFTP support enabled by default. Command-line usage: sshd start (stop, restart, test).
Note:
ssh (from OpenSSH), sshfs (from FUSE), and plink with psftp (from PuTTY) are available on the client-side.
16. Other servers: FTP.
The FTP server in 4MLinux (ProFTPD) is preconfigured to work out of the box. Command-line usage: ftpd start (stop, restart, test).
Note:
lftp is available on the client-side. Additionally, you can try one of the following 4MLinux scripts: ftp, sftp, and fish.
17. Other servers: SMTP.
The 4MLinux Server uses Postfix with preconfigured ports (see this post) as its mail transfer agent. It comes with Procmail and Fetchmail to create a complete mail delivery system. The "smtps" support is provided by stunnel (see point 12 above). Command-line usage: smtpd start (stop, restart, test).
Note:
By default, for security reasons, the incoming traffic (from the Internet to your server's ports: 25, 465, and 587) is blocked by the 4MLinux Firewall. You can unblock these ports by editing the /etc/firewall/config file.
18. Other servers: DNS.
4MLinux uses BIND as its DNS server. When started, it points your name server (in /etc/resolv.conf) to localhost. Are you still able to surf the Internet? If so, this proves that your BIND is up and running :-) Command-line usage: dnsd start (stop, restart, test).
Note:
By default, for security reasons, the incoming traffic (from the Internet to your server's port 53) is blocked by the 4MLinux Firewall. You can unblock this port by editing the /etc/firewall/config file.
19. Other servers: NFS.
The 4MLinux Server makes use of nfs-utils and rpcbind to run its NFS daemon. NFS exports can be manged manually or via Webmin (pictured below). Command-line usage: nfsd start (stop, restart, test).
Note:
By default, for security reasons, the NFS traffic (ports: 111, 1110, 2049, 4045, 4046) is blocked by the 4MLinux Firewall. You can unblock these ports by editing the /etc/firewall/config file.
20. Other servers: proxy.
The 4MLinux Server incorporates Polipo (with an optional Tor support) as its proxy server. Polipo has its own web interface (http://localhost:8123). Command-line usage: proxy start (stop, restart, test).
Note:
Go to the /etc/polipo directory to learn in details how the proxy server in 4MLinux works.
0 commenti:
Post a Comment