CentOS 5 :: How's System V Ids Intialized At System Boot Time
Aug 31, 2009
We have 2 applications set as S96 and S98 at rc3.d and rc5.d simultaneously. Both applications create a system V shared memory segment by calling shmget.If the system boot at runlevel 5, both applications can obtain their shared memory segment id correctly, i.e. 98305 and 131074 individually. While there is a root owned segment id 32768 takes first seat on the list. This is the id list:
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 having dual boot system(windows 7 and Fedora 12).When i switch on my system.It show the the timer 3 sec in order to get boot selection window(means window which asks that what to start fedora 12 or windows 7).I want to increase this time from 3 to 10 sec.
I've been having a problem on my AMD based machine, 4cpu, gigabyte ga-ma78gm-s2h Mobo, 8GB mem, two 2 terabyte Sata HDs.One thing I've found is that any kernel after 2.6.32-17 has a randomness at boot time whether the system will completely boot or not.
For instance just today I downloaded and installed 2.6.32-24
It fails to boot (I've tried cold boot, warm boot).Running its repair also fails to completely boot.My experience is that if I keep trying it "may" eventually boot but I believe there was some change after 2.6.32-17-generic that's causing the problem.Because as with 2.6.32.23... which also fails to complete bootup many times... eventually my guess is that 2.6.32.24 will also boot "sometimes".But why does 2.6.32.17 always boot for me? Something changed and its not my setup.
why, after booting to windows for any length of time that upon rebooting to Fedora the system time is 3 or 4 or 6 hours off? Sure, it is easily fixed with ntpdate but is there a more permanent fix?
For some reason, every time I shut down and reboot my machine, the system time advances four hours. The local time here is EDT (-4hrs UTC). I have it set correctly in Yast and have the 'hardware clock is set to UTC' checked. However, for some reason, the next time I boot, the system time will be ahead four hours.
I'm running a dual-boot; Lucid and Win XP on a HP Pavillion.My time settings are about 8 hrs off between the two operating systems. If I correct the time in Linux, it will be wrong when I boot in Windows. If I correct it in Windows, it will be wrong again next time I boot into Linux.Besides the obvious solution of removing Windows from my machine (which I'm not ready for), what should I do to fix this?
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.
when I installed Ubuntu 9.10 I put in one time setting but it was wrong, and now I don't know where to change it. I tried to change the time preferences, but on reboot I am back to the wrong time.
I know the data is in there somewhere and I can change if I knew where it was.
How to make the system boot faster by removing the idle time between 5s to 10s? bootchart attached. It is Ubuntu10.04LTS by the way. One more hint, the screen black out for ~4s after "Begin: Running /scripts/init-bottom... Done." I don't know what is going on during that 4s, but my best guess is there is a way we can get rid of it. Bootchart can be found here:
LIVECD of 11.3 Gnome works fine in my old PC. I installed several times and each time system freezes/crashes during boot. I am linux newbie, so, I am trying to figure out my problems. In Livecd I noticed Hardware info list's my SATA disk as IDE. Driver Modules: "ata_piix"Attached to: #24 (IDE interface). Is it right? I have posted Hardware information output in 01: None 00.0: 10105 BIOS [Created at bios.186] - Suse 11.3 install problem My machine specs are: Intel DG31PR motherboard, Intel core2duo, 3 GB DDR2 Ram, 250 GB SATA harddisk
have all ways been hiding in the background read not say a thinglets start well i look after 2 dell poweredge 2650 with 12 gig ram installed servers has been running fine onwell i though it was time to upgrade to 5 all went fine till reboot Memory for crash kernel (0x to 0x) not within permissible range ! well what i have been reading this is the norm for now What is mean by ignore it? LoLwell so i did the system keeps boot till i get to this linesbin/mingetty: /sbin/mingetty: cannot execute binary file alot, and it shows. INIT: Id "5" respawning too fast: disabled for 5 minutes ...so maybe its a memory issue so took 8 gig out left 4 in the system now it reboot alls good with only 4 gig of ram installed so is there a way to fix it to use all the ram can i get the system boot on 4 gig and then add the 8gig later on
I just recently installed ubuntu 9.10 in my upstairs computer. It is a single boot system.Downstairs I have a dual boot system. I have windows vista and ubuntu 9.10 installed. It worked fine. I wanted to make this a single boot system and uninstall ubuntu 9.10. I cannot get rid of the grub bootloade
I am running a server (multipale roles). The base OS is Centos 5.2 and an xen kernel... The system is usually headless... Most of the work i do is also through terminal. However I have come across multiple situations that require me to visually have access. The problem I am running into is that the remote desktop built into the system dosent enable remote access to the system intill i have looged in on the system? What are my options? or is their a way to boot remote desktop with the system?
I had installed CentOs 5.3 on a Virtual Box machine (v. 3.0.10) and then I needed more free space to upgrade to CentOS 5.4 on partition /. I wanted to substract some space from /home partition in order to add some more free space to /. Thus I used a gparted live cd (v. 0.4.8-1) that it is a debian live cd. I resized the partition as I wished and every operations went successfully, but when I tried to reboot the only message that I see its 'GRUB' and nothing else happen. If I start again with the gparted live cd, everything seens to be fine as the partitions are there but I can't boot the system.
I'm installing CentOS for the first time to run mythtv on (I previously used Fedora, but the new version cycle was too quick). As part of the instructions I'm using, I am told to run system-config-boot (to ensure that centosplus kernel is loaded on boot). The problem is, I cant find this option in my installation of CentOS. Another option I have is to manually edit the grub.conf file, but I'm not sure exactly how I should edit it.
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 did a yum update to install quite a few updates to my Centos 5.3 x86_64 system. Updates included kernel and xen which required a reboot. It must be a month or so since I last updated. The updates seemed to go fine - but when the machine restarts it goes through the bios screens which seem to detect all the hard drives etc - but then the word "Grub" appears at the bottom of the bios screen - and the system hangs. It doesn't appear to respond to keyboard input. The system is using linux raid in case that is relevant.
I am able to boot a centos5.2 live CD and look at the Logical volumes - and all appears in order to my untrained eye. I have also mounted the /dev/mdo as /tmp/bootx (boot volume) and had a quick look at /tmp/bootx/grub/grub.conf and /tmp/bootx/grub/device.map and again - I can't spot any obvious problem. I note that before the updates - my default boot was "1" and now it is "0" though this appears reasonable because the xen and non-xen images seem to be listed in the opposite order to earlier updates. I have set it to boot non-xen by default - and this has always worked in the past.
I realise that the recent updates may be a coincidence - and whatever is wrong may have occurred earlier. I cannot think of anything I have done which could have broken grub though. I can probably restore my boot volume to the state it was before the updates. I should have a backup from this morning - as luck would have it. Is this a safe thing to do - or do I need to restore both boot and root to keep them consistent. I would prefer not to restore the root system unless I have to - as this would cause some data loss. However I need advice as to whether yum and other things will get confused if the boot volume is restored in isolation.
I just installed CentOS 5.5 on my machine and the installation appeared to complete successfully (it said it was successful). When I rebooted and tried to get into my new CentOS, my system completely locked up during the startup. According to the progress bar, it got stuck on the first-run configuration. I have not yet been able to boot into the OS. I am attempting to create a dual-boot system. I already have Windows XP installed on a separate hard drive. The GRUB loader works fine and I can choose either OS to boot into, it's just the CentOS won't finish booting. Windows is completely unaffected.Since I'm assuming the problem stems from the installation, I'll list the steps I followed.
1. Obtained the .iso image from a network drive at work (I am installing on my work machine). The image is dated May 17, 2010.
2. Burned the image to a DVD.
3. Booted from the DVD and chose to install using the graphical interface.
4. Checked the DVD. The installer verified that CentOS could be installed from it.
5. Picked my installation and keyboard languages.
6. Chose to create a custom layout for my partitions. On my second hard drive, I created the following partitions:
- Swap (8196MB, twice my system RAM) - ext3 (100MB, mounted to /boot) - ext3 (remaining drive space, mounted to /)
7. Picked my timezone (did not use UTC since Windows will handle setting the system time)
8. Set my root password. You don't get to know ;)
9. Did not choose to install any additional packages besides the KDE desktop. I wasn't sure what I'd need so I checked the option to customize later.
10. The installation than started and 15 minutes later, it told me it had succeeded and to remove the DVD and reboot.
11. Upon rebooting, I let the GRUB loader boot into CentOS (side note, I'd prefer if Windows was the default OS but that's something I should be able to Google on my own).
12. The startup looks like it's going fine until it gets to the first-run configuration, at which point the entire system locks up and requires a hard reboot. I've tried several times since and it always locks up at the same point.
1) does it overwrite existing configuration files that is will i need to reconfigure every service after running yum update
2) If somebody pushes the reset button or electricity to the system is reset while yum update is running what will happen i think there can be two stages to that
a) if it is still downloading while the electricity to system is reset
b) it is installing while electricity to system is reset
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
So 2 days ago everything was all fine on my machine. Has been for about a month, but all of a sudden as of yesterday I have no sound, I am seeing IRQ interupts on boot, During boot I am seeing file system is not clean, , and swap space is being used for the first time while doing normal task, etc. These are 2 new hard drives in RAID 1 with ReiserFS. I should have used a newer FS but thats a whole other argument.
Anyways here we go. The system is Debian Lenny amd64 Physical RAM 4GB + 6GB swap /var/log/messages
Code: Feb 21 07:35:09 Sarah kernel: imklog 3.18.6, log source = /proc/kmsg started. Feb 21 07:35:09 Sarah rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="3994" x-info="http://www.rsyslog.com"] restart code....
My fedora 11 (2.6.30-102) spends a long time while initializing services on
"Starting system message bus:"
---------- Post added at 08:47 PM CST ---------- Previous post was at 06:33 PM CST ----------
Auth is LDAP.
There's a 3.5 years old bug in redhat bugs database, that's still not resolved,regarding dbus trying to use ldap auth, before ldap service is started.Workaround is to change ldap config to soft binding.
3.5 years for a bug that affect enterprise users - are you there redhat?
I am trying to configure a system to boot Windows XP, CentOS 4 and RHEL5. I have one hard drive that contains both Windows XP and CentOS 4, and a separate drive that contains RHEL5. Until recently, I only had one SATA cable, so I could only connect one drive at a time. Under this configuration, everything works fine. When the RHEL5 drive is connected, I can boot into it. When the Windows/CentOS drive is connected, I can dual-boot into either OS. (GRUB was configured on this drive automatically when I installed CentOS into a new partition.)
Opening the box and moving the SATA cable is a lot of trouble, so I finally got a second SATA cable and enabled both SATA0 and SATA1 in the BIOS. I currently have the Windows/Centos drive as the primary, and I can still boot into both Windows/Centos. Now, I want to add RHEL5 to menu, but I can't find the file GRUB is using to present its menu at startup.
I have configured GRUB before on other systems, but I just know the very basics, such as where the grub.conf file should be. So, I spent a whole day reading advice online and asking friends who might have experience with these issues. Here are the steps I have taken so far:
I confirmed there is no /boot/grub directory, and /etc/grub.conf is a broken soft-link to /boot/grub/grub.conf. I did a find for grub.conf, which found nothing. I did a find for menu.lst, which found one item -- an example GRUB config file in /usr/share/doc/grub-0.95. I noticed that when CentOS boots, I see the GRUB commands printed to the screen, the first of which is:
root (hd0,2)
So, I did a grep -R "(hd0" * at the / directory, which also found only one item -- the example menu.lst file in /usr/share/doc/grub-0.95. I discovered that I can go to the command line grub from the grub menu and do:
cat (hd0,2)/grub/grub.conf
The cat command returns a printout of the grub configuration the system is obviously using. I didn't create this file, but the titles are identical to what I see in the GRUB menu, the default boot is Windows, and the timeout is very short. This must be the file. It looks like:
default=2 timeout=5 splashimage=(hd0,2)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.9-89.ELsmp)
[Code].....
I've also tried making the RHEL5 drive the primary drive. In that case, I can modify the existing /boot/grub/grub.conf file and see my changes at the GRUB boot menu. However, I can't get Windows to boot in this configuration. I've done a lot of google searching on the topic and added map commands to make Windows think it is on the primary drive. But, I'm still unsuccessful on this front as well. I think I'm closer to solving the problem with Windows/CentOS as the primary. However, if you think I will have more success with RHEL5 as the primary drive, I can provide more details as to my current grub.conf on that drive in a later post.
