Articles in the Recovery Category
Debian, Featured, Headline, Linux, Recovery, Shell »
Maintaining a subversion repository can be a hard task if you don’t work with the right tools. Today, when technology advance daily, we are still vulnerable to “fate”: crashed harddrives, corrupt RAM, network outages, power failure or other “evil” problems. Even if you are a conscientious administrator you will not be missed by “Murphy Laws”, only if you are a “bastard” lucky guy (I’m a bastard lucky administrator from hell but you are not). In the next article I will try to show you, how-to create a good backup of …
Clustering, Debian, Featured, How-to, Linux, Recovery, Shell »
Monitoring is one of the most vital part of all online business right now. A server what fail to deliver its content to a client it’s a big problem, because of this server disruptive service or downtime is our the worst enemies. Some downtimes are impossible to be predicted and monitoring your system is the best thing you can do. Did you ever asked yourself what means 99% availability? 7 hours per month of downtime. 7 hours for a client can be very frustrating.
Share this post
…
Debian, Hacking, How-to, Kernel, Linux, Newbie, Recovery, Security, Ubuntu »
When we auditing a Linux system we have a lot of good tools to monitor unexpected changes and unexpected behaviour of a system. Earlier we talked about rkhunter as a system check for rootkits and now, as an alternative, we will talk about chkrootkit (Determine whether the system is infected with a rootkit).
Share this post
Hide Bookmarks
Debian, Featured, Hacking, How-to, Linux, Newbie, Recovery »
Protecting your bootloader is intended for a desktop workstation and not for a production server. Why protecting your bootloader ? Because with a simple boot in single mode a malicious person can change your root password or steal your data. Protecting your bootloader with a password will protect your computer to run in single mode without your permission, but will not protect you to boot from a bootable cd if you don’t also protect your BIOS.
Share this post
…
Debian, How-to, Kernel, Linux, Newbie, Recovery, Tuning »
By default, a Linux, is waiting direct input of a person / sysadmin when is crashing with kernel panic/oops. Obviously is very important to know or to see directly the dumped screen, but sometimes in production environments is better just to reboot itself without any intervention and debug the problem with the system online. Off course for debugging and seeing the dump you will need to install and configure kdump, but that is another story (I will probably write about that soon).
Share this post
…
