Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Posting this because all I found on line were multiple links to a single google post about this error.
On a RHEL5.10 system this morning I did a "dig" and got the error:
timer.c:331: fatal error: RUNTIME_CHECK(isc_time_now((&now)) == 0) failed
Clearly the message is related to time and in the US this past weekend we switched to daylight saving time (in my case we went from EST to EDT). Initially I thought it was because the system I was on didn't...
We run a Nagios master server with Nagios Core 3.3.1.
We have nrpe version 2.12 on the servers being monitored (clients) and use check_nrpe v2.12 from the master to interrogate them.
The version of check_disk on the clients is v1.4.14 (nagios-plugins 1.4.14).
Typically we setup the nrpe.cfg on the clients to monitor each individual disk by its device name e.g.
On receiving an install media today I tried mount it on my RHEL5 system:
mount /dev/hdc /mnt/cdrom
But that errored out:
mount: block device /dev/hdc is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/hdc,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
During an issue overnight I attempted to run the latest Dell Dset version 3.5.1 for 64bit on RHEL 6.1. This didn't complete. It just hung.
By doing "ps -ef |grep dset" I was able to see the dset child of the dset bin file I'd kicked off.
By running "lsof -p <pid>" on that child's PID I was able to see it was creating a log for its run in opt/dell/advdiags/dset/report/temp1391539132.89/logs/dset/dset.log (note that the temp# changes on...
Today I was creating a new init script on RHEL6. This isn't something I've had to do often.
I ran into the common problem that although the new script successfully started and stopped the service from command line and also started it on reboot it did NOT stop it before the server went down when the shutdown was done.
The reason for that is because on RHEL they run a killall script that checks for files in /var/lock/subsys and only run the "stop" portion...