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. 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.
23. Yeay!
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)