1. Open your terminal:
$ useradd -m -s /bin/bash hrp $ passwd hrp $ cd /home $ ls -l $ mkdir hrp $ chmod 0700 hrp $ chown -R hrp:hrp hrp
1. Check if FTP service is exists.
2. Install vsftpd
$ sudo apt-get install vsftpd
3. Command line to check your FTP service.
4. The default vsftpd configuration file is /etc/vsftpd.conf. You need to edit this file using text editor such as vim:
5. Uncomment these lines.
6. Type this command.
7. Add new FTP user to this file.
8. Restart your FTP service.
9. Test FTP connection from other machine.
10. Click to allow access.
11. Tada =)
1. Add new directory.
$ sudo mkdir moa_hrp
2. Initial the directory.
$ sudo cvs -d /var/lib/cvsd/cvsrepo/moa_hrp init
3. Check your CVSROOT directory, there is no passwd file.
4. Create a new user.
5. Add new repository to the CVS server.
6. Add this line of code.
7. Restart your CVS service.
8. Try to login.
1) Install Nagios. Type this command line:
2) It will go through, and ask you about what mail server you want to use:
3) Choose your type of email configuration.
4) It will then ask you about the domain name you want to have email sent from. Again, fill that out based upon your needs.
5) It will ask you what password you want to use.
6) Confirm your password.
7) Installing the application.
8) We need to edit a few files. Start by opening /etc/nagios3/nagios.cfg. Use this command:
9) Search for check_external_commands, and turn the check_external_commands=0 into check_external_commands=1
10) Now, restart apache by running:
11) We need to edit /etc/group. There should be a line like this in there:
Change to this:
12) Now, we need to edit the /var/lib/nagios3/rw files permission with:
13) Again, restart your nagios3 and apache services.
14) If you want to monitor http and disk space, type this command line:
15) Change to this.
16) Do the same thing for this file:
17) Change to this.
19) And you should be good to go! Happy monitoring!
1. The default form MySQL Server is to be binding to localhost (127.0.0.1), which means it only accepts connections from local applications.
2. To change it, open up your terminal. Find port 3306.
3. Change to root user and edit the below file.
4. Place a hash (#) at the beginning of the line.
5. Restart your MySQL Server.
6. Test remote connection.
1. Download JBoss AS 7.1.1.Final from this website: [ LINK ]
2. Downlaod JDK 1.7 from this website: [ LINK ]
3. Install JDK 1.7, I’m using JDK 1.7Update21. Move jdk-7u21-linux-x64.gz file to /opt
4. Extract the file.
5. Put JAVA into the path of root.
6. Check that JAVA is now in the path of root.
7. Create an “application” directory in /and move jboss installer into it.
8. Extract the installer.
9. Rename jboss-as-7.1.1.Final to jboss-as. This is not strictly necessary, but it will save you the bother of changing the start up script later.
10. Since we will want to run JBoss as non-root user with minimal privileges, we will create a user “jboss“, who will own the JBoss files and JBoss will run under this account.
11. Switch to the user jboss and type this command; ‘java -version‘ to verify that JAVA is now in the path of user jboss.
12. To create our JBoss script, we will copy the jboss-as-standalone.sh script located under /application/jboss-as/bin/init.d
13. Change line 5 from it’s original ‘# chkconfig: – 80 20‘ to ‘# chkconfig: 234 80 20‘
14. Set the JBOSS_USER (refer a) and set the jboss path (refer b).
15. To run JBoss as service and enable start up at boot, make the script we created above executable and add it to our chkconfig so it starts at boot.
16. Try reboot your operating system. If still unable to start after reboot the OS, refer to this screenshot.
17. Mark jboss as startup services.
18. Bind your server IP address to these lines.
19. Start your server by using this command: $ service jboss start | stop | restart
20. Let’s start with adding a Management user. Login as root, naviate to /application/jboss-as/bin
21. Follow the prompts, some defaults are provided.
22. Restart JBoss to reload the changes.
Crontab is the program used to install, deinstall or list the tables used to drive the cron daemon in Vixie Cron. Each user can have their own crontab, and though these are files in /var/spool/cron/crontabs, they are not intended to be edited directly.
Each user has their own crontab, and commands in any given crontab will be executed as the user who owns the crontab. Uucp and News will usually have their own crontabs, eliminating the need for explicitly running su as part of a cron command.
$ crontab -l
$ crontab -e
$ crontab -r
$ crontab -v
(credit image: link)