Four winning ways to monitor machines through Web interfaces

Tags

Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Four winning ways to monitor machines through Web interfaces

11-04-2008

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

Four winning ways to monitor machines through Web interfaces

11-04-2008 02:00 AM
System administrators need to keep an eye on their servers to make sure things are running smoothly. If they find a problem, they need to see when it started, so investigations can focus on what happened at that time. That means logging information at regular intervals and having a quick way to analyse this data. Here's a look at several tools that let you monitor one or more servers from a Web interface.

Source...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Programming

Application behaving in 3 different ways on 3 different machines

Hello. During the holidays I've been developing an application on my desktop computer at home. I setup a repository on github, so when I got back to work I cloned the repo to my laptop. It wouldn't work. The app is comprised of a client and a server, strangely enough the server would segfault...

2. Linux

Routing via several interfaces for hosted virtual machines

My setup consists of a hardware node, which hosts several virtual machines (OpenVZ, to be precise). The hardware node has two network interfaces (<ifA>, <ifB>) connected to different subnets (<networkA>, <networkB>). I want to route the traffic of certain VEs over <ifB> while routing the other VEs...

3. UNIX for Dummies Questions & Answers

Ways to Access Files on Unix Server via Web

Hi all! I'm a web developer with a question. We have a contractor that is working on a project that requires the user to access a ton of files on the clients Unix server. He has plans to built a VB interface for on site windows users to access those files and wants us to develop a web based...

4. Shell Programming and Scripting

how to monitor 25 different digitalUnix and Sunsolaris machines

Hi I am a new Junior System Administartor..currently in our team we have around 25 different machines comprising of Sun-Solaris and digital Unix machines...and every morning we telent into the system to check 1)all demons are workin fine 2)all cpus are up 3)the memory is okay But...

LEARN ABOUT MINIX

reboot

REBOOT(2)							System Calls Manual							 REBOOT(2)

NAME

       reboot - close down the system or reboot

SYNTAX

       #define _MINIX_SOURCE 1

       #include <unistd.h>

       int reboot(int how, ...)

DESCRIPTION

       Reboot() is used to close down the system.  It allows several ways of shutting down depending on how:

       reboot(RBT_HALT)
	    Halt the system and return to the monitor prompt.

       reboot(RBT_REBOOT)
	    Reboot the system by letting the monitor execute the "boot" command.

       reboot(RBT_PANIC)
	    Cause a system panic.  This is not normally done from user mode, but by servers using the sys_abort() kernel call.

       reboot(RBT_MONITOR, code, length)
	    Halt the system and let the monitor execute the given code of the given length.  (code is of type char * and length of type size_t.)

       reboot(RBT_RESET)
	    Reboot the system with a hardware reset.

       Reboot() may only be executed by the super-user.

DIAGNOSTICS

       If the call succeeds, it never returns.	If something went wrong, the return value is -1 and an error is indicated by errno.

SEE ALSO

       shutdown(8), reboot(8), halt(8), sync(1).

NOTES

       Minix  can not return to the monitor if running in real mode, or if started from MS-DOS.  This means that most of the reboot functions will
       change to a reset.

AUTHOR

       Edvard Tuinder (v892231@si.hhs.NL)

																	 REBOOT(2)

UNIX and Linux RSS News