General :: Autostart An Application After CentOS 4.4 Reboots
Jan 28, 2010
I am fairly new to linux.We have a machine running CentOS 4.4 and sometimes the machine has to be rebooted. Each time after the reboot, I have to SSH in and manually restart one of our application. I have been reading about doing this online and I am a little confuse.Seems like there are multiple possibilities for starting things up. My finding suggest using the inittab file. Then my question is what runlevel do I pass in? Should I use runlevel 1, 2, 3, or 5? Once the runlevel is determine, then how should I name my startup script? I know to use "S" but what number should I give it? Or, another way to approach this is to put my autostart script in the /etc/rc.local file?
How can i do autostart my apllication in thistaion (light weight OS) i know i have to write script, but i am confused how to write? my application is squid 2.6.
I have a single kernel with 2 menu entries in grub like following:
Boot(gfx) Boot(text)
First entry boot the fedora in graphical mode running the gnome. Second entry boot the fedora in text mode.
First thing is working fine but i want to know how to do the second thing. i added 3 at the end of second entry in syslinux.cfg and after booting it dropped me at console asking for login.
So how to autologin in runlevel 3 and start autostart an application(e.g python script)?
I am using an Ubuntu VPS(Virtual private server) with SSH access. I run my applications(mangos-realmd & mangos-worldd) in SSH terminal and they start up fine. But when I close the SSH terminal they close! but I want it so that when I close my SSH terminal that those programs remain running, and also want them to start up each time I reboot my system. I am found out with rc.local this is now solved or what-not
Running CentOS 5.5 on a Dell PowerEdge 710 with a mirrored RAID. System randomly reboots leading to MySQL table corruption as its not a graceful shutdown. Here is the output of the getinfo shell script [URL]. Some data has been obfuscated such as public ip addresses. Prior to posting this a full hardware diagnostic was run by the Data Centers support team which turned up nothing.
Output of last|grep boot|head
reboot system boot 2.6.18-194.11.1. Tue Sep 21 03:24 (05:51) reboot system boot 2.6.18-194.11.1. Sun Sep 19 12:10 (1+10:53) reboot system boot 2.6.18-194.11.1. Sat Sep 18 23:20 (1+23:43) reboot system boot 2.6.18-194.11.1. Sat Sep 18 18:20 (2+04:42)
CentOS 5.5, I've installed Synergy to share my keyboard/mouse and it works fine. Now I'm trying to get it to load automatically at boot.
The command is simple, "synergyc <computername>".
I've tried putting the command (see above) into rc.local I've tried putting the command in a script and referencing in in rc.local I've followed the instructions for building it into init levels (2-5) with chkconfig
I have a new CentOS 5.6 installation. It was installed in text mode. I have changed the line id:3:initdefault: in /etc/inittab to id:5:inittab. Even after that change, gdm does not start automatically. gdm is installed, and can be started from the command line. I have put DISPLAYMANAGER="GNOME" and DESKTOP="GNOME" in /etc/sysconfig/desktop.
I have a newly installed CentOS 5.4 which is having shutdown problem, if I try "shutdown -h now", the machine will poweroff then reboot instead of poweroff completely. how to debug this problem?
Hardware: Gigabyte G31M-ES2L, 4G RAM, Sil 3112A PCI SATA card, 6 SATA disks and one IDE disk. I have disabled all power on options in BIOS. Software: CentOS 5.4, software RAID, samba
I received a new Cyberpower CP1000PFCLCD UPS today. I let it charge for about 6 hours.My server is a former desktop PC with the following specs:MSI MotherboardAMD Athlon XP 2000+ CPU768 MB DDR RAMDual 80 GB HDD running RAID 1 (Disk Mirroring)After shutting the server, router, and backup drive down and plugging in the UPS, I did the UNPLUG test where you unplug the UPS to see if everything stays on.My Router and Backup disk both stayed powered on, but the Server immediately rebooted.Does anybody have any ideas how I can fix the server rebooting problem? It should be staying on just as everything else.
I am trying to build a fat client on an old pc. I have CentOS 5.3 installed standalone. Basically when the user turns on the pc, it automatically logs into a linux account and the desktop appears. I have installed rdesktop 1.60 to connect to a Win2008 server. From the command line or from a launcher icon I created on the linux desktop everything works fine. What I want to do is for the system to automatically execute rdesktop after the automatic login to linux. So I used the Sessions GUI. (Go to System, then Preferences, then More preference, then Sessions.) Within the Sessions GUI, I clicked on the "Startup Programs" tab and click on the "Add' button.
I type in : rdesktop -f servername (where -f gives you full screen, and servername is the name of the windows server) This works a couple of times, then it fails. When you reboot the linux pc, it will auto login, then show the rdesktop screen for a split second, disappears and then it shows the linux gnome desktop.
I've found a workaround, but the workaround doesn't make any sense to me.I suspect I am running into a bug of some sort.I've tried to search for a solution, but the search terms are too broad and I can't seem to find anything useful.I have a CentOS 5.5 system that I've set up Virtualization on (presumably Xen, right?). I have a RHEL 5.4 Guest OS using "Full Virtualization" method.When I was installing the RHEL guest, the entire server rebooted just as the RHEL guest was booting for the first time.Thinking that odd, but coincidental, I just let the Host server reboot and then started up the RHEL Guest again.The reboot happened again and in the same spot! When I say the server rebooted, I mean black screen...pause...bios screen.I finally managed to get the RHEL Guest booted by removing the DVD that I had in the DVD drive and disconnecting it from the Guest OS in VMM. Very, very odd. I can reproduce this behavior by simply booting a Guest OS with a DVD in the drive (so far I've tried only RHEL guests).
The reboot happens at the same place in the Guest boot process. It's when RHEL starts the UDEV script. Actually, a few seconds after the RHEL system displays "Starting udev" message. I've looked in both the CentOS and RHEL messages log and found nothing.It's not a huge deal at this moment, but I will be sending these servers out into the field and I can't control what the end users of these systems put in the DVD drives.
I just installed 5.6 using the x86_64 netinstall - all appeared to go well, albeit a little slowly. At the end of the install i rebooted the machine but CentOS won't load. If I select the CentOS option from grub (only other option is 'other') the machine instantly reboots.
Only options selected for install where 'server' and 'server gui'.
Editing the CentOS options shows the following but I've no idea whether this is correct or not (assume it is):
I have several systems experiencing this issue, but the "worst case" system at the moment is a system where there are 2 dual-port PCI-X e1000 cards, and two on-board e1000e PCI-express card.What happens is maddening. If the /etc/sysconfig/hwconf is removed, and kudzu is not run, and the 6 interfaces each have a corresponding script:
Now what happens defies explanation. The only way I can be sure to make the e1000e first-listed-in-pci-order e1000e device always eth0 is to remake the initrd and add e1000e to the initrd.If I do not do that, eth0 might be the onboard night, it can also be the first port on either of the dual port cards.So eth0, eth2 and eth4 all take turns being eth0. This was not an issue in the EL-5.1 timeframe. This is certainly new to the EL-5.2 timeframe and thus far is not possible to control because the system does not load eth0's driver alias in order, and the enumeration of the PCI devices causes what seems to be random labeling of the first interface.
This is a particular problem in that identical hardware systems will come up with different eth0 interfaces , and on a single system, without the /etc/sysconfig/hwconf (which calls "eth0" something different from what was originally in the /etc/sysconfig/network-scripts/ifcfg-eth0 HWADDR directive).I need as little auto-magic as possible, I can live with PCI-bus order and driver load order is the order ethernet devices appear in, I cannot use the software in a state where what is "eth0" is randomly determined and the only way I can nail it down is to run kudzu, generate a hwconf AND brand the network interfaces in the network-scripts with HWADDR. I've been using EL since 6.2 and this is the first time I've ever encountered a situation where the enumeration rules (which are ancient at this point) over-ridden by something.
Version-Release number of selected component (if applicable): EL-5.2 series.The random enumeration of PCI devices and the subsequent assigning of eth0 to a random NIC is not on every reboot, and does not seem tied to a power off scenario vs a simple reset or warm reboot. Over the course of 0 reboots , eth0 should have moved between 2-3 times.Packages that seem relevant.
I've been trying to get Ubuntu on my computer for months now and after having googled no relevant cases which may help me I would like some help.
I am trying to install Ubuntu on my computer (which already has windows and I don't want to lose it yet)
I have already burnt 3 CDs yet the problem is the same each time, that's why I believe the problem does not come from the burning. I checked the md5sum and there was no problem.
However when I try to install Ubuntu (or sometimes during a live session) after partitionning my computer and selecting mounting points, having "format" checked on the concerned partitions, the installation goes halfway through the "copying files" process and my computer simply reboots. More precisely, in the middle of installation the screen is replaced with the loading page of Ubuntu (like when you start with the live CD) then my computer reboots, no questions asked (not even to remove the CD, it reboots with the CD in it... while during a manual shutdown it would open the tray and ask you to close it)
What's the easiest way to make things autostart in KDE? The only method I know is to make links to the applications and then put them in the KDE autostart folder. Last time I did that, I had a lot of trouble with not being allowed to make the links unless I was root. Is there a simpler way?
I write code check.sh and add the following line as it's first line:Quote:#!/bin/sh -eThen make it's permission as executableThen coped it to the following destination:Code:cp Scripts/check.sh /etc/init.d
I just installed Fedora 13 on an HP Z400, and it's stuck in an endless reboot loop (lives 2 seconds before rebooting). It's a 64-bit machine and seems to meet all the hardware requirements.
I want to boot the 'Finnix' distro from a usb. I have unetbootin which can set it up on the usb, but it can't allow me to preserve files after rebooting. Is there anyway to do this, maybe do it manually or use another software to install it on the usb?
For ubuntu there is no problem getting files to be preserved after reboots..
I'm a complete Linux beginner who wrote his first little script.I'm writing an 'installer' for it (so I can share it with friends) and I'm wandering if there is a universal method to add it to autostart in all Linux distributions.I was thinking about cron/crontab but it's not the best choice, as writing an uninstaller which removes a specific line from crontab is out of my league. I'd rather copy a *.desktop file to autostart folders and then be able to remove them.BTW do you have to put *.desktop files in ~/.config/autostart in Ubuntu, but ~/.kde/Autostart in Kubuntu even if they are shell scripts?
I'm trying to get a script to autostart and hitting some snags. I know the script works, because I can manually launch it from a terminal window. I've perused the forums and followed similar advice to put the script in the /etc/rc.d/init.d directory and then create a symlink in the rc5.d directory (S99my_script) I've even tried appending ". /etc/init.d/myscript" to the .bashrc file
I've managed to get the machine to autologin "myuser" upon startup (that's the owner of the .bashrc file I edited), but still the script won't start when myuser auto logs in. the system default is set for password protect on screen save so if I simple let that happen, as soon as I exit screen save the script launches, so it almost works.
I have this extremely simple script called startmyth:
Code: #!/bin/bash sleep 10 export DISPLAY=:0.1 exec /usr/bin/mythfrontend & when I execute it as ./startmyth, it works fine. But when added to Gnome's startup applications (System > Preferences > Startup Applications), Mythtv does not start! What gives?
Use python as example, I have 64bit python 2.4.3 yet I can't found rpm for 32bit one so I try to build it.Use default make or make --enable-readline is ok, python make cannot use CFLAGS, can use OPT and LDFLAGS to add -m32, yetit seems can only search for 64bit lib, or else crush.[Moderator edit: Moved from CentOS-4 to CentOS-5 forum.]
I have a pool of approximately 1,000 Linux servers and I would like to get a total count of reboots that occurred on those servers each month. I would like to collect this reboot count at the end of each month. Can anyone tell me what the best way to get this count.
If I issue a shutdown -rF now, it will force e2fsck's on all the volumes when it reboots. But once the checks automatically finish, does it restart normally? I want to run e2fsck's on all my volumes, but dont want to stay the probably 5 hours it will run, so hoping someone knows for sure what happens.
I've decided to give openbox a try with Debian testing. I set up my right-click menu exactly how I want it, and everything else is set up perfectly. I installed trayer and tint2, along with nitrogen. I added the following lines to my ~/.config/openbox/autostart.sh file, but things aren't loading/restoring as they should. Tint2 and trayer don't load at all, and nitrogen isn't restoring my wallpaper. All I get is a black screen with my cursor, but the ability to right-click and open the menu, so it's not like X is dead. I did set the default wallpaper by issuing the command nitrogen /home/john/Pictures/Wallpapers, where "Wallpapers" contains all of my background images.
Here is my autostart.sh file: Code: # Autostart file for openbox nitrogen --restore & sleep 2s && tint -c /home/john/.config/tint/.tintrc) & (sleep 2s && trayer --expand true --transparent true --alpha 255 --edge bottom --align right --expand true --SetDockType true --widthtype request --margin 130) & I do have proper content in the .tintrc file located in /home/john/.config/tint/tintrc. Am I doing something wrong here?
I've got it to the point it will run when you login by adding a line to the /etc/xdg/lxsession/Lubuntu/autostart file. Added "synergyc 111.111.1.11" and it works perfect. So the main question is, how can I add that line somewhere, somehow to start on boot and not by login?
unclean shutdowns/reboots. Whenever I boot/restart, I notice the message "/dev/hdb1 (and hdb2) was not cleanly unmounted, check forced." Then fsck(?) scans them without errors, and everything continues normally. FWIW, hdb1 @ hdb2 are ext2, /boot & /tmp respectively, whereas all other partitions are ext3. Could that (ext2) be why? I checked halt, reboot, umountfs, umountnfs.sh, and umountroot in /etc/init.d, and nothing jumped out at me, though I'm not exactly sure what I'm looking at/for.
