General :: Debian - Run A Script Constantly In Background?
Mar 19, 2011
I have a perl script which runs a mini webserver allowing me to do various things. I'd like to have this script run when the machine starts up, and constantly run in the background.How should I achieve this? I want the script to regardless of whether anyone is logged in or not, so I can't put it in any bash-related files.
I'm running Ultimate Edition 2.0 64bit. When I'm running Firefox and I'm not doing anything on it it starts to use the disk intensively. I checked on terminal using the top command and it IS Firefox using up to 85-90% of the resources. Anyone know what the problem is here? Can it be hacked? I already uninstalled and installed back again and it still doing it.
I'm using Debian 6.0 on an Optiplex 960. My system constantly freezes. When I move the mouse (or press a key on the keyboard), my system resumes execution for approximately 2 seconds, and then freezes again. This problem is not restricted to Debian,'ve ncountered similar problems with other linux distributions on my hardware. I was wondering if anyone else had encountered this problem before, or had any ideas about how imight be resolved. I'm copying my hardware information below.CPU INFORMATION
processor: 0 vendor_id: GenuineIntel cpu family: 6
I am running a minimal debian "Squeeze" system with xfce and recently noticed a marked slowdown in my samsung nc10 netbook performance; with all other applications closed htop revealed the following process eating up cpu which explains the slowdown. Previously cpu idled at about 10%. The user is root unlike all the other processes:user:rootpu:70% command:/usr/bin/x :0 -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
So I'm having troublesome issues with Debian 8.2, one of them being really costly to my productivity. This issue started maybe a month or so back, and has been continuing since. Laptop is a Toshiba C50-B-14D
During every freeze all those happen:
Screen freezes (The whole display becomes frozen, with only cursor movement - Time displayed stays frozen too)No keyboard input (even Cap & Num Lock leds will not dim once pressed)Power button (pressing once will do nothing - I have to hold for an unhealthy shutdown and reboot)Touchpad Input Works (Cursor responses to movement only, clicks/change on-hover do not.) Fans become quiet
Today at 11:46, it happened while just running Chromium. At the time:
*XFCE4 Power Management Plugin Presentation Mode [on] Charger was connected
Here is the syslog (I know this isn't useful as it doesn't show what's causing the issue) the freeze happened at 11:46 and 11:57 is when I rebooted back into debian.
Code: Select all----------------------CUT------------------ Oct 30 08:31:01 Badook rtkit-daemon[1315]: Supervising 4 threads of 2 processes of 1 users. Oct 30 08:31:01 Badook pulseaudio[1364]: [pulseaudio] pid.c: Daemon already running. Oct 30 08:41:09 Badook kernel: [Â 727.002897] perf interrupt took too long (2502 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 Oct 30 08:42:02 Badook pulseaudio[1312]: [alsa-sink-ALC233 Analog] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write!
[Code] ....
I also started noticing an INFO rcu message during startup:
Code: Select allroot@Badook:/# cat /var/log/syslog.1 | grep -i "rcu" Oct 29 14:39:33 Badook kernel: [Â Â 0.000000] Hierarchical RCU implementation. Oct 29 14:39:33 Badook kernel: [Â Â 0.000000] Â Â RCU dyntick-idle grace-period acceleration is enabled. Oct 29 14:39:33 Badook kernel: [Â Â 0.000000] Â Â RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=2. Oct 29 14:39:33 Badook kernel: [Â Â 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
I have an external hard drive (1TB MyBook) mounted via fstab by UUID to a directory. When copying/writing/reading a lot of files from it, it randomly unmounts and remounts as a different device.
It'll start as /dev/sdb1, I'll set a lot of files to copy to it and then it'll unmount and re-acknowledge itself as /dev/sdc1, the file copying process will crash and the current directory in terminal will display an I/O error. Running mount -a remounts it back to the directory specified in fstab as /dev/sdc1 and the loop continues. If it's just idling, there's no issue, only does this under load.
Im currently installing debian on my old server, its a 64bit computer, so i've downloaded the amd64 for this project. But under the Basis Installation, of this cd image, im getting a debootstrap warning every time i want to continue the installation, the last warning i remember was something coreutils_6.10-6_amd64.deb (Something like that, not totaly sure), and im lost, can't find anything closely related to the subject.
I use WLM (And yes, I realise odds are this is a problem on microsofts side) and almost every time claws mail connects WLM returns a new certificate. Valid, but I have to constantly accept or deny the certificate. Why is WLM pumping out fresh certs all the time and how can I fix this?
Whenever this pops up whatever I have at the moment shows "Signature status: No certificate issuer found" and the other shows "Signature status: Correct".
I setup Debian a few days ago and everything was working fine. On a routine reboot to test a start-up script I turned the monitor on and realized that I could not logon to the machine locally. None of my keyboard input was making it to the username field but random things were happening. Every now and then it would say stuff like incorrect username or spontaneously jump to the password input field and then say incorrect password. I've rebooted a couple times, even without a keyboard attatched and still am seeing this. In /var/log/auth.log I show gdm going nuts trying to validate usernames.
Oct 18 12:15:16 Eva gdm[3287]: pam_nologin(gdm:auth): cannot determine username Oct 18 12:15:16 Eva gdm[3287]: pam_nologin(gdm:auth): cannot determine username Oct 18 12:15:16 Eva gdm[3287]: pam_nologin(gdm:auth): cannot determine username
Using Wicd and it keeps dropping out or telling me "bad password" when the password is in fact correct. I even know it works because the first couple of times it worked, but the connection wasn't sustained for more than a few seconds each time. My reasoning is my wireless is functional in Ubuntu, there's no reason it shouldn't be in Debian. Wireless network card is ASUS PCE-N13. Ralink driver is installed. WPA-supplicant is installed. Gnome Network Manager is also present, though I've heard that it doesn't support my particular situation.
Im running a Debian 2.6.26-2-amd64 webserver with apache2 only on a Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz that has 2GB of ram in it. I installed htop a few days ago and have been looking on it for a few days now. the server idles on about 80~ish tasks constantly with arond 20 apache tasks/connections to it all the time and the cpu usages of the 2 cores at about 1% each. but asoon as more apache2 connections/task get started and the servers tasks reach 120-140~ Apache2 timesout if you try to go to the webpage i host on the server. when it's back down to around 80~tasks you can reach the webpage once again. why is this ? what's causing this to happen ?
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 am running ubuntu on my netbook and use vlc media player, for some reason when I play 720p videos they get choppy and freeze constantly, is there a way around this or the videocard that comes with the netbook is having problems supporting it ?
I have 2 computers on the same network that i need to link together to transfer files 1 is a web server the other is a minecraft server. the problem is that the file transfer will be constant as the minecraft server will constantly updates files on the web server and I dont want it to go to the router then to come back to the web server. I want to add a second network card to each computer and link them together and use this second connection to transfer the files is it possible?
Anyone know why each time I boot up the machine the cube background image goes away and the background colour is left. This image i am placing is in Apparency/Skydome
I'm currently running ffmpeg from a windows machine and realized it's rather redundant as I could be running it from the Debian (headless server) machine instead. What I'm trying to achieve is to get ffmpeg running as a background job...
Effectively, as far as I've gathered, this should be enough:
But it's not working - when I run the command from terminal to check it, it works fine... but when I try to run it as a background job it creates the job but no output is generated. According to posts around the web, other people have been successful at running background jobs like this for transcoding static files.Should it be done differently or is this an issue with ffmpeg itself?
I noticed recently my XFCE 4 is missing its background. I seem to have falled back to some gray background. I noticed icons/files that should be in desktop is also missing. Seems like desktop is broken somehow Whats wrong? The single panel holding window buttons etc is still working. ( debian jessie )
insmod png if background_image /usr/share/images/desktop-base/spacefun-grub.png; then set color_normal=light-gray/black set color_highlight=white/black
I am running a dual-boot of LMDE and Debian Squeeze XFCE, and I actually have a Debian XFCE question. How can I tell what is running in the background. I have been tweaking my Debian install since I first installed it about 3 weeks ago, and I keep adding to the RAM usage. What is the best way to see what else is running out there and whether or not is it necessary?
Running lenny with compiz/xfce4 and it seems to only affect a few things but I notice it mostly with google chrome. Whenever I open a new window it pops up behind chrome. This is very annoying. Chrome bug or config problem?
I'd tried to run HDD bench mark at my Debian Stable called iozone3. It performed I/O actions which took too long. Ctrl+C to terminate process. Everything went as always. It just terminated. Upon completion of program I used laptop for some more time. During shutting down X-Desktop shut down normally. Terminal window was showing command line with lines <Stopping this and that daemon...> but instead of normal black colour background with white text it changed into red background with white text. What does it mean? Is it safe to restart laptop?
I've spent a good part of the day wrestling with replacing the grub background image. I did my homework and over the past few days read every thread and suggested link I could find on this forum. I had a clear idea of what needed to be done. Spacefun had quite a laugh at my expense! It was not fun at all. First, I put images in /usr/share/images/desktop-base and made changes in /etc/grub.d/05_debian_theme to point to the image I wanted to use. Yes, I updated grub but spacefun had some sort of deathgrip on the setting.
So I threw an image in /boot/grub. Well, Grub found that and spacefun was gone but there was no background image when it booted - only a black background! At this point, I just surrendered and replaced spacefun-grub.png with the image I wanted and it finally worked. There are links in /usr/share/images/desktop-base/ that point to /etc/alternatives/ which in turn point back to the original file in /usr/share/images/desktop-base/ which I think may be the root of the problem but I didn't just want to start deleting links willy-nilly. Does anyone think that might just set things straight? This whole process is several steps backwards in customizing ability from what it was with grub and GDM a few years ago. This is NOT progress!