I have a machine that experienced some troubles with some of the real time stuff that I'm running. One lead that I have is that NTP daemon may have moved the time, causing false timeouts.
How do I find out if NTP daemon did indeed move time at all? Any logs? I do see NTP daemon restart in /var/log/messages, but I don't know if time adjustment should be there as well. to clarify: I need to understand it from the logs, after the event. May be 2 days after the time was adjusted. Running commands to see the current status doesn't help.
I have a switch tray on my computer and I installed opensuse in one of the hard drives that I have but as I switch between the windows hard drive and opensuse the time changes all the time. For example it's 10pm right now and if I switch the hard drive to opensuse the time automatically gets adjusted 4 hours back and then I fix it and when I switch back to my windows hard drive the time goes forward 4 hours. I check both region settings and they are both set to NY Eastern time. Why is it doing this?
I am using the default CVS available in Fedora 9. I initiated the CVS server by cvs -d /usr/local/cvsproj init To check-in and check-out the following exports commands are used export CVS_RSH=ssh export CVSROOT=:ext:swathi@SERVER:/usr/local/cvsproj
I shall explain problem by taking an example. A project was checked in long before (for example the checkin date is 25 Feb 2010). And today (i.e. 21 June 2011) I checked out the project from the repository. After checkout, the date of the project in the repository is changed from 25 Feb 2010 to 21 June 2011. This date is set to all the subfolders in that project. But the files in the project retains the checking date i.e. 25 Feb 2010. Why the check-in dates are getting updated/changed to the system time after doing check-out.
I have an HP w1907 LCD monitor and when i try to use it with ubuntu 9.10 it displays oversized in the screen. I have tried to adjust it using the preferences/display (changing height/width) but cant seem to get it right. There are no linux drivers for this unit at HP. How can i get the size/aspect adjusted?
I'm just wondering what the limits for time are. I have a program that always takes exactly 20 ms, so I assume this is the lowest it can measure, but I want to see if there's some sort of documentation of this.
get the values for the user time and system time for a process.i have tried getrusage to get values of ru_utime and ru_stimebut these don't seem to be correct
you can refer to this ubuntu thread for context, but i'll sum up what i'm trying to do here to spare the reading. basically i want to be able to schedule a filesystem check with automatic repairs at the next boot time. but i'm not sure if this will try to automatically fix errors which is what i want to do. the reason i want to do this is because i experienced a power outage (the machine was not plugged into an UPS) and i want to make sure everything is ok.
I'm trying to check my server's bandwidth usage in real time, installed the following programs but none worked so far.
Iptraf - No results even when using iptraf -u Tcptrack - Error : pcap_loop: cooked-mode frame doesn't have room for sll header Iftop - No results, everything 0b
Are there any programs that displays bandwidth usage in real time and actually works on VPSes? Or getting real time bandwidth usage on a VPS is simply impossible?
Would like to know what command can be used to check for other user accounts on my system. Note, not presently logged in users like whocommand just a command to know other users?
I have a program that i want to install on only RHEL 3 and 4. It does not support RHEL 5. How do i check if a Reh Hat OS is 3 or 4 and not 5.Similarly i need to check this for SUSE 9 and 10. For RHEL, i am trying to see uname -a and also cat /proc/redhat-release. How do i make sure that if the target system is RedHat 3 or 4. and in case of SUSE, how i decide for SUSE 9 or 10 and not other.
I know one way is to enforce rules on the passwords, use at least one uppercase, lowercase, number, special character, and ensure that the password length is at least 8 characters, etc...
Is there an additional way to prevent weak passwords? I heard of "John the ripper". Has anyone successful applied that?
I have NFS fileserver that has served me well for more than year. But recently I noticed that it has started to reboot on its own very frequently, almost once a day! It is most likely not a power related issue as I tried changing UPS/power sources, but no help!So my question is:Is there any log file where I can check which is causing the reboot? There may not be a single logfile, but I need some point to start the investigation!
i have problem during boot my F11 , the problem is :
Code:
checking file systems /dev/sda7 : superblock last time ( etc... ) /dev/sda7: Unexpected inconsistency ;run fsck manually (i.e,without -a or -p option) ***an error occured during the file system check ***dropping you to shell:
I have doubts regarding storage: How to configure the Events of Storage Processor? What are performance issues will come daily in a critical production server? What are first steps for disk performance Check? What are first steps for Storage Processor performance Check? What are first steps for MetaLUN performance Check?
When I use the `date' command on RHEL5, I can get the time shown in 24 hr format. I wonder if the time can be shown in 12 hr format. But I don't want to use the `date +FORMAT' to do that, neither `alias date='date +FORMAT''. I just want a simple `date' to show time in 12hr format.Is there any configuration file about the 12/24 hr format? Is the format related to the value of the environment variable 'TIMEFORMAT'? I can't find its default value by 'set | grep -i timeformat'.How can I know what the current format is? I mean, when I use `date', I can get "Sun Sep 19 13:22:50 CST 2010", which seems like 24hr format; but when I use `hwclock', I can get "Sun 19 Sep 2010 01:23:05 PM CST -0.174299 seconds", which seems like 12hr format.
When booting Fedora 11, my system hangs for a very long time on starting udev. Sometimes I get an I/O error. However, my hardware is fine. I do eventually get in to the system.
I am running my Ubuntu 32 bit server on top of Windows 7 64 bit with VirualBox. It's a 2 core Atom. It's been working good for about half a year. But the last about 6 weeks the system time only in Ubuntu is going slow. About -8 per 24 hours! I can only guess because I have more things running in my Windows 7 and Ubuntu.
I can set it right by coping the hareware time to system time with this command:
Code: hwclock --hctosys
I want to run a crontab to have that command run every minute. But it don't seem to run.
I want to get the system idle time till a mouse move or a key press. How is it possible to get it from a char terminal running through ssh/telnet as well as a from an X-terminal session?
I have a desktop PC with Fedora, Ubuntu and Windows installed and grub used for multibooting. But time in Fedora is always 5 hours behind. If I change the time in Fedora, then Windows and Ubuntu will be 5 hours ahead of the current time. I don't understand how to fix it.
I use the time command to measure the wall-clock time of a GPU implementation of an algorithm. When I time the CPU execution of the algorithm time returns a negligible sys time. However, when I time the GPU execution time returns a sys time that is around 20-30% of the total time. If that time was comparable with the negligible sys time of the CPU I would achieve a speedup of a few times higher.
I suspect that the increased sys time is because of the GPU usage, which, I assume, takes some time for the OS because of the drivers etc. I am not sure though, and it is important to figure this out because it will improve my results a lot if I can ignore the sys time and use just the user time for speedup calculations. Also, is there a way to see, in detail, what is the sys running and takes so much time. I am thinking that I might be able to see if it is the driver indeed that causes this delay.
What are others' views and experience regarding automatically checking filesystems (running fsck) at boot time?To be more clear, I have left the ext3 filesystems on this machine set to require checking after a fixed number of mounts by using tune2fs with the '-c' option. I've done this mainly because of the following (from the tune2fs man page):
Code:Youshould strongly consider the consequences of disabling mount-count-dependentchecking entirely. Bad disk drives, cables, memory, and kernel bugs could all corrupta filesystem without marking the filesystem dirty or in error.e using journalingon your filesystem, your filesystem will never be marked dirty, so it will not normallybe checked. A filesystem error detected by the kernel will still force an fsck on the nextreboot, but it may already be too late to prevent data loss at that pointBut what does anyone else do? Is there really much risk to disabling this automatic checking
I know that uptime prints the time a machine has been up and running, but is there an easier (reliable) way to get the date of the start up than counting down from this output?I tried looking around /proc, but didn't find anything of relevance. There's also a line like this on my dmesg: [ 0.673492] rtc_cmos rtc_cmos: setting system clock to 2011-03-14 14:26:52 UTC (1300112812), but I'm wondering if this method is distribution and kernel version agnostic.
I need to write a small application which needs to detect if the system time is changed by an another application/user and perform some action as soon as it is detected (maybe log the data that time has changed, along with info about which application/user changed it).
How can this be achieved?
I have good programming experiences in shell script, c and beginner level in python. I don't need to know when it was changed, just need to know who/what changed it. The system uses NTP to sync the time, but it is also possible for anyone/any application to change the time(for eg: using the simple "date" command as well).
My Linux system was last rebooted few hours ago. But it seems little confusing for me to figure out the exact reason behind it. I guess following command should justify what i meant to say.
Code: # date Wed May 11 13:22:49 IST 2011 # last | grep "May 10" reboot system boot 2.6.18-194.el5 Tue May 10 17:35 (19:46) root pts/1 XXXX Tue May 10 17:24 - 18:18 (00:53)
[Code]...
My question is Why the uptime is saying that the system is up since last 47 min.It should be more than 1 day if i m not wrong.
1. How sum of system time and user time can be greater than real time ? 2. Even though my program is not waiting for any I/O the real time is smaller than system time as shown
root@chaitu:/home/chaitu/Desktop/Chk# time ./new real0m0.001s user0m0.000s sys0m0.004s
Every time I boot up I have to go through a disk check and then restart, how do I stop it from happening? When the disk checks happening I press escape and it usually says its deleted inode something because it has zero Dtime or some thing similar and also a paragraph of repeated lines saying something like all system files need alsa base.cnfg it will be ignored in a future release then the disk check completes and it restarts and is fine then, also sometimes it says dev/sda5 (my ubuntu partition) was not cleanly unmounted check forces. Is their a way to stop this happening as it ends up taking ages just to login.
When I start the computer I receive the message that the drive that contains the /home partition has an error. If I press "F" the screen says that the drive is no ready, that I can wait, cancel or manually recovery. If I wait, in about 1 minute, the system starts normally. If I press "M" to repair manually, then I press fsck to repair the disk and apparently repairs the disk. But everytime I start (power on) the computer, Ubuntu always checks the disk and gives a dialog where I can: press F to attempt to fix the errors, I to ignore, S to skip mounting or M for manual recovery
