BibSonomy ::  user :: lystrata ::

Welcome to the Ubuntu Manpage Repository This site contains hundreds of thousands of dynamically generated manuals, extracted from every package of every supported version of Ubuntu, and updated on a daily basis. Traditionally, manpages are browsed on the command line. This project renders all such manuals included in Ubuntu in an HTML, web-browsable format.

"To Set the BIOS for Linux 1. Power on the workstation. 2. Press the F2 key at the Sun logo screen to enter the BIOS Setup menu. 3. Go to Advanced > Integrated Devices. 4. If necessary, change the Configured SATA as option to AHCI. 5. Press the F10 key to save your changes and exit the BIOS."

Save a file you edited in vim without the needed permissionsI often forget to sudo before editing a file I don't have write permissions on. When you come to save that file and get the infamous "E212: Can't open file for writing", just issue that vim command in order to save the file without the need to save it to a temp file and then copy it back again.   :w !sudo tee % Annotated link http://www.diigo.com/bookmark/http%3A%2F%2Fwww.commandlinefu.com%2Fcommands%2Fbrowse%2Fsort-by-votes

"LVM cannot stop/remove LV, cannot stop/delete dead RAID situation. Hi, I am having an issue with LVM and RAID in some failure cases: It seems that any operations on a LVM LV (lvchange, lvremove, etc..), require this LV's metadata to be readable. In case a LVM LV is setup ontop of a RAID 0, or a RAID 5 for instance, if two disks are lost from the RAID array, the array dies. Now that the array is dead, I would like to recreate a new RAID 0 or 5 using the remaining alive disks and some new ones. For this reason, I'd like to stop the previous dead RAID using mdadm. However, because the LVM LV does still exists, it seems to have a handle on the dead RAID, as shon below: # /opt/soma/bin/mdadm/mdadm --stop /dev/md/d0 raid manager: fail to stop array /dev/md/d0: Device or resource busy Perhaps a running process, mounted filesystem or active volume group?"

Here's a dirty script I wrote to install nagios and Lilac on a clean CentOS 5.4 install.  This script doesn't care about anyone other than itself (it'll change the mysql password for instance) so may not be entirely perfect for your needs.

Central Loghost Mini-HOWTO This page is simply a collection of open source tools you can use to glue together your own centralized (syslog) loghost. Included are example configuration settings so that you can configure your loghost in a manner similar to mine. There is very little that you need to read and understand in order to use these tools. Also, these tools are widely used and therefore easy to get help with on internet mailing lists. I established a centralized location for syslog collection in order to facilitate: Log reporting real time alerting periodic (several times per day) summary reporting Log storage long term archival for possible later analysis Tools used: UNIX hosts (Linux and Solaris) Modified logcheck script(s). Syslog-NG Swatch though I'm slowly moving to SEC, this page will be updated once I've completely switched Splunk for a GUI interface Stunnel

This page provides a basic tutorial on understanding, creating and using regular expressions in Perl. It serves as a complement to the reference page on regular expressions perlre. Regular expressions are an integral part of the m//, s///, qr// and split operators and so this tutorial also overlaps with "Regexp Quote-Like Operators" in perlop and "split" in perlfunc.

How check_mk monitors logfiles The monitoring of the contents of logfiles is an especially challenging task for a Nagios administrator. The key difficulty is, that log messages are event based by nature - whereas Nagios is based on states. Check_mk's logwatch mechanism overcomes this problem by defining the critical state for a logfile as "no unacknownledged critical log messages". At the beginning of the monitoring a logfile starts in the state OK - regardless of its contents. When a new critical message is seen in the file, it is stored on the Nagios server for reference by the administrator. The state of the logfile changes to CRITICAL and stays in that state unless the administrator acknowledges the messages. New critical messages arriving while in CRITICAL state are simply being stored and do not change the state. Check_mk provides a webpage logwatch.php that displays log messages and allows the delete (and thus acknowledge) them in an easy way:

There are a number of times in which you find yourself needing performance data. These can include benchmarking, monitoring a system's general heath or trying to determine what your system was doing at some time in the past. Sometimes you just want to know what the system is doing right now. Depending on what you're doing, you often end up using different tools, each designed to for that specific situation. Unlike most monitoring tools that either focus on a small set of statistics, format their output in only one way, run either interatively or as a daemon but not both, collectl tries to do it all. You can choose to monitor any of a broad set of subsystems which currently include buddyinfo, cpu, disk, inodes, infiniband, lustre, memory, network, nfs, processes, quadrics, slabs, sockets and tcp.