i was playing around with c++ recently and for laughs and giggles i came up with this little program
Code:
#include <iostream>
using namespace std;
int main ()
{
[Code]....
theoretically that should be an infinite loop but it in fact does terminate eventually echoing out 'FIRE!'
just wondering if even though in theory this should be an infinite loop (a number repetedly divided by 2 should never reach 0 thus the conditions of the loop should never be satisfied, hence infinite loop) perhaps in practice limitations of the variable types prevent this?
I think i came across a bug in X server in squeeze. I would report it to the bug tracking system in debian packages but the think is I am not entierly sure about it.When i start X (whether it is through startx or service gdm start or auto startup through init when the pc boots) the computer PC seems to lock up.The screen goes black right after X initializes and before anything is show in the screen and if i wait a about 10 minutes the monitor either goes in standby or out of range. PC seems unresponsive to both keyboard commands and mouse but my LCD screen in my G15shows the time skips 1 sec every 2 sec (from 19:22:22 goes straight to 19:22:24).
I have a custom 2.6.33 kernel which i build but it happens with both 2.6.32-trunk and 2.6.32-3 offical kernels from the squeeze repository so i dont think that this is the problem.My PC is a P4 3.75Ghz with 2Gb RAM and an NVidia 6800GT with the binary drivers from nvidia. I have tried diffrent versions from my grapgics drivers (NVIDIA-Linux-x86-173.14.25-pkg1.run & NVIDIA-Linux-x86-195.36.15-pkg1.run) with no change in the behaviouThis is the syslog from the time my pc started and then "stuck". I left it for some time before i hard reset it
I want to figure out what is going on in this small script.Its really strange.I think its the infinite loop again.All I want to do is to collect some data from the zenity dialog box in an array and then echo it.Here is the code
Code: #!/bin/bash #export PS4='+${BASH_SOURCE}:${LINENO}:${FUNCNAME[0]}: ' debugging info
I am trying to develop a process monitor, or use existing monitors to achieve the below given actions.
1) Restart a processes if it crashes. 2) Restart a processes if it is stuck in an infinite loop.
The sample code below describes the structure of the process.
while(1) { statement 1.... statement 2.... while (1) {
[Code].....
The goal is to restart the process if it is stuck in a loop, inside the outer while loop. Given this scenario, what would be the most efficient way to monitor such a process?
A sample solution would look something like this: statement 3 will write to file1 every time it is executed and we know that the maximum execution time of the outer while loop is 30 seconds. A second, timer driven process, checks for file1 being modified every 30 seconds. If the file is not modified, process 1 will be restarted assuming, process1 is stuck in a while loop.
I'm using debian etch and I've installed some automatic updates, after that some programs weren't running. So I restarted the pc. Now that the computer boot up normally but when it reaches the login screen it just emit a sound in the pc's speaker,he login screen flickers and is showed another login screen again and again and again (it's automatic). I can logon using the option single-user mode in the grub options, any idead on how can I fix it?
I have a java server console program that I have configured xinetd to start when connection comes in on a given port and then the program runs in an infinite loop receiving inputstream from telephone exchanges. The thing is, when a new chunk of stream comes from the exchange xinetd forks a new process each time. I tried setting the wait parameter to yes and restarted the deamon, but no success. How can I stop this behavior and have the deamon just direct the stream to the process already running? Am I missing something in my config or is it just incorrect?
My config is as follow: defaults { instances = 60 log_type = SYSLOG authpriv log_on_success = HOST PID log_on_failure = HOST cps = 50 10 } includedir /etc/xinetd.d
And then my actual config, service aos_larmar { socket_type = stream protocol = tcp user = root type = UNLISTED wait = yes instances = 256 server = /home/gunnl/java/start.sh port = 5204 disable = no }
My server OS is, Red Hat Enterprise Linux ES release 4 (Nahant Update 7)
When I boot one of my machines, it gets as far as GRUB, then proceeds to a blank screen for a second, and then repeats the cycle all over again - ad infinitum. I have tried previous kernels on the list with the same results Also, I cant boot into recovery mode either.
I have run Memtest successfully from the GRUB options and no errors appear in the results. I have tried booting from a Live CD and here I get as far as the "OS choosing screen". When I then select one and hit Enter, the screen goes blank and the machine reboots as before.
I upgraded to 10.10, system rebooted but it is stuck at a constant loop.
I can go into safe graphics mode and things look fine except compiz isn't running. I have tried going into login and changing it to log me in automatically but the problem remains.
I've tried using my previous kernal and I have the same issue as this newer one.
I've tried loading gdm from CLI and the problem is still there.
I'm doing a dual boot Ubuntu 11.04 and Windows 7 on my Asus UL80v. When I restart and keep going into Ubuntu I'm fine, but I think if I go to Windows and then restart, the infinite start up happens, and I'm currently stuck in this. It'll go to the OEM screen, then a black screen with a cursor, then it goes black, and then back to the OEM screen and so on and so forth.
Luckily I have Ubuntu 10 on my flash drive, so I'm booting to that while I try to figure out this. Which reminds me, when I use the flash drive, there's an option to boot to local disk which also does not work, if that's worth anything. Before this happened, I ran check disk on windows because I ran into some partition troubles. There seemed to be no problems, and I can still access the drives from this flash Ubuntu.
I installed Xubuntu and was thrilled to see that it had already setup my Brother HL-2140 USB laser printer.However, there is something seriously wrong with the setup. When you try and print, even a test page - it just churns through the entire paper tray printing nothing. Also, when you restart the computer it tries to print the jobs again. I went to Printing and selected the printer but could not find where you could see the print job queue. I did see it during troubleshooting and was able to delete the jobs on the troubleshooting screen.
there's 2 scripts that i want to run when my server start.I a bit new to linux, i found that i could use the script rc.local to run things at startup, although, what i want to run is 2 infinite loop, so the first loop run but not the second.
It happens really randomly. Suddenly keyboard and mouse stop to react. Screen freezes. However if I have for instance skype running during that "crash", I can still continue to talk over internet. For me looks like x serwer crash. Xorg logs however are empty. I had to hard reboot only to get control over pc (magic sys key + SUB) only works. Trying switch to another session is not working. I run Slackware 13.1. Kindly asking to help me to solve that irritating issue. I pasted errors usually I find at Xorg.0.log.old after hard reboot only
Code: 2.6.35.4 #2 SMP Tue Sep 14 19:33:55 CEST 2010 i686 Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz GenuineIntel GNU/Linux OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce 8800 GT/PCI/SSE2 OpenGL version string: 3.2.0 NVIDIA 195.36.15 OpenGL shading language version string: 1.50 NVIDIA via Cg compiler
I have recently been running into the "EQ overflowing" message. It has been happening when I open an image with gimp or a xls with open office. I noticed some were having this issue with earlier kernels. I am using the nouveau driver to run two nvidia cards with three monitors. I am currently running the 2.6.34.6-54.fc13.x86_64 kernel. Here is the output of my Xorg.0.log file:
Fedora 15, fresh install.I changed the wallpaper from default to a solid colour. After switching between gradient to colour the system crashed logged me out and upon logging in it simply runs endlessly accessing my harddisk but never actually loading the desktop.I can kill X and reboot, but it's the same problem waiting for me on restart. I really don't want to re-install or delete users (to put it in context, I just spent 3 days trying to install Fedora because Anaconda doesn't know how to install GRUB correctly).
I have just upgraded from 10.4 to 10.10 (x64), and now when I run gnu screen the new shell session goes into an infinite loop displaying:
Quote: Linux dave-desktop 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:45:36 UTC 2010 x86_64 GNU/Linux Ubuntu 10.10
Welcome to Ubuntu! * Documentation: [URL]...
0 packages can be updated. 0 updates are security updates.
repeatedly until I hit CTRL-C and break out of screen. I tried tmux and that did the same thing, so it is a problem with the shell initialisation rather than with the screen program. However I can start bash, zsh or sh directly in a terminal with no problem.
Last week I dropped my keyboard, came back about an hour later, and without realizing the keyboard was on the ground hitting a random button I went to add a bookmark to my menu panel(I think that's what it's called). An unknown amount of the selected bookmark then posted to my menu panel and now i am not even able to select my Applications, Places, or System options without the bookmarked task opening. Is there anyway of clearing out that entire menu panel and having a fresh start?
EDIT: All I did was delete the .gtk-bookmarks file and restart the computer. There were still alot of theme on the panel but i was able to delete them and everything returned to normal.
I was possibly overzealous in uninstalling packages using deborphan. I uninstalled various libraries and progams that I don't use (ppp, gimp, etc.), but I must have touched something useful, since the machine will no longer boot.
I thought this might cause a few problems, but expected to be able to recover, at least using the Recovery Mode. This isn't the case, sadly.
The main symptom is an infinite boot process, even using the recovery-mode boot. Things proceed as normal (grub screen, few lines of startup messages), but then a ton of text starts pouring onto the screen. It scrolls much too fast to read, and the Pause/Break key won't stop it. I do notice that there is a lot of talk about devices and udev, but can't make out more than that. The text doesn't obviously repeat, so I tried just waiting it out, but gave up after a couple hours.
For some reason my Conky is making my machine do infinite DNS requests to the last host I'm connected with. For example, if I visit forums.debian.net it'll start the infinite DNS request to this host. If I close the navigator it stops. If I try to connect to irc.freenode.net it starts the DNS requests. If I disconnect it stops. Why is it happening?
Running Ubuntu 10.10. I was trying to get mythtv going and in my infinite wisdom decided to reboot to fix a install problem. Anyway now I get a "windows classic grey" login prompt - which seems to be a symptom of the more serious next problem: My desktop is black, mouse is black, taskbar exists but I only see the clock. No desktop icons etc etc.
Not sure where to post this, I am runing 10.04 LTS, 64 bit and things have been great, until..... I activated a Ubuntu One account and once I did, my Ubuntu One folder would immediately close upon opening and my downloads folder would immediately close upon opening. I delt with it, no big deal. So I decided that I need to get my crap off the Ubuntu One account so I downloaded them all from the website onto my desktop. Now none of my folders immediately close upon opening and ever couple seconds my desktop flashes and a windows quickly opens and closes stating "starting file manager".
I found a couple of posts the looked like fixes, but nothing has worked. clicked off show_desktop in gconf-editor which stops the "starting file manager", but does not stop the folder from immediately closing. I also found this, [URL]... but I don't know hoe to apply the patch nor if I should. I have tried some other things, but I cant find the threads again to provide. I believe one was the killall Nautilus then apply Linux Essentials, which I don't think even ran at all.
I need to rename the resulted searched files from a loopI have the following code:
find . -name DOC* | while read i do find $i -type f -name '*.txt' done
basically, I am searching for all txt files inside any folder starting with DOC name.this code is working fine with me.I need to rename those .txt files to .txtOLDOS: Ubuntu 10.4Bash shell
I just cant seem to understand loops. i havent put the loop in yet but what i would like is the user only to have 3 tries at guessing number then exit if wrong or it says "correct if right" tbh i dont even know if the above code is correct. i have tried several ways and position of the loops but each time is comes out wrong
I am trying to do some shell programs. I tried some sites regarding the while loop, they give the structure as: Code: while [ n1 -lt 500 ] do echo $((n1+100)) done
But the below code also worked for me: Code: while ((n1 > 500)) do echo $((n1+100)) done By using (( )) I could use while, for. But the documentations didnt follow this way. I mainly use this for datastructure programming.
In the code segment below is a for loop I am having some considerable difficulty with. It just keeps iterating endlessly and totally ignores the 70 times limit specified. I can't ever remember having this problem before and am absolutely Clueless.
Code: for ( x = 0; x < 70; x++ ) { fputs ("CSN00", target); fprintf (target, "%d", userid);
I've got a 'nested' for loop which has a grep in it, if the grep fails there's no output - however the error code is still $0 and the second for loop is still entered, there's also a grep in the second for loop.I guess ultimately what i need to know is whether there's a way of making grep generate an error code. when no results are found?
