**** BEGIN LOGGING AT Thu Dec 08 02:59:57 2011 Dec 08 10:34:20 Hi, i have a strange problem with cron. About one minute after my only job has finished, the cron daemon uses ~95% of the CPU. Is this something anyone else has encounterd Dec 08 10:35:40 Zmurf: is everything ok with your job? Dec 08 10:37:16 reisei: It seems so. It is a wrapper around ntpdate that only run it under certain circumstances. The job finishes and i do get a log entry in the cron log and in my own shellscript log Dec 08 10:38:23 Zmurf: have it any waiting for something? Dec 08 10:38:57 well yes. it does some sleep inside it, and it also calls ntpdate Dec 08 10:39:16 reisei: http://pastebin.com/QxK665nv Dec 08 10:40:29 reisei: so far, i have only used the cable case in the top, so the rest of the script is not even executing Dec 08 10:41:02 reisei: root@igep00x0:/etc/init.d# cat /var/log/ntpupdate Dec 08 10:41:02 Start NTP-date and time update Dec 08 10:41:02 Just use the avalable cable interface Dec 08 10:41:02 8 Dec 10:32:53 ntpdate[1181]: adjust time server 178.78.255.254 offset 0.025941 sec Dec 08 10:41:02 NTP update prcess has ended Dec 08 10:41:03 Zmurf: why you don't want to use ntpd? Dec 08 10:41:45 Cron can do this if the job is waiting for something, I guess. There are no ideas else, sorry. Dec 08 10:42:25 this script runs fine then you do it in console? Dec 08 10:42:52 several reasons. I only want to run it if the errors are too big, i will need to control which interface it runs on and other reasons Dec 08 10:44:06 reisei: yes, runs fine in console. the log i gave you is from running it with cron. The script does its job, but around one minute after it has finished, cron runs amok. If i replace my script with "ls" this does not happen Dec 08 10:45:30 what do you mean by replace? Dec 08 10:46:06 # 1 * * * * ls Dec 08 10:46:06 1 * * * * /etc/init.d/ntpupdate.sh > /var/log/ntpupdate Dec 08 10:46:31 If i change which line is commentend out, cron does not run amok Dec 08 10:47:26 try to delete the loggin part "> /var/log/ntpupdate" Dec 08 10:48:37 reisei: ok. testing Dec 08 10:50:32 still happens Dec 08 10:51:10 so, guess, something is wrong with the script. Dec 08 10:51:58 maybe i should try to use ntpd instead, but i will need to run other scripts also. Hmm.. .. well i guess i could try to remove arbitrary parts of the code and hope for the best Dec 08 10:53:02 it cant be that i change the clock and that this confuses cron? Dec 08 10:53:11 what's wrong with ntpd for you? Dec 08 10:53:41 Zmurf: if you changing the clock for a high value it can confuse the whole system Dec 08 10:54:07 :-) i move it up from 1 jan 1970 :-) Dec 08 10:55:55 Hmm... i guess i could restart cron from inside my script :-D Dec 08 10:56:14 I don't know cron very well so have no prognose about its reaction for that time changing Dec 08 10:56:40 *prognosis Dec 08 10:58:06 reisei: it is ok. you have helped me with what i needed: someone to talk to me about the problems Dec 08 10:58:08 :-) Dec 08 10:59:29 Zmurf: :-) you're welcome Dec 08 11:00:21 if i called exit in the beginning of my script, cron did not run amok. my current assumption is that is has to do with the timechange Dec 08 11:02:01 what is amok, btw? Dec 08 11:03:09 Running wild, uncontrolled, that sort of thing. maybe i missspell it Dec 08 11:04:24 Zmurf: oh, I thought that's some kind of process :) Dec 08 11:05:15 reisei: hehe ok. now i understand the confusion. Anyway, i have done a /etc/init.d/cron restart after each call to ntpdate inside my script and now it works just fine! Dec 08 11:06:59 Zmurf: so, the point was in time changing... interesting. Dec 08 11:16:03 angstrom: 03testlab  07yocto * raf556d367b 10testlab/beagleboard/eglibc/XFCE-NetworkManager-image/build-id: beagleboard: XFCE-NetworkManager-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 118249f9ec841ce677fd12c36c2ca6bf20a068dc Dec 08 11:16:13 angstrom: 03testlab  07yocto * rbe7cffece8 10testlab/beagleboard/eglibc/systemd-image/ (build-id installed-package-sizes.txt installed-packages.txt): beagleboard: systemd-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 118249f9ec841ce677fd12c36c2ca6bf20a068dc Dec 08 11:36:21 angstrom: 03testlab  07yocto * r692e416baf 10testlab/beagleboard/eglibc/systemd-GNOME-image/ (build-id installed-package-sizes.txt installed-packages.txt): beagleboard: systemd-GNOME-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 118249f9ec841ce677fd12c36c2ca6bf20a068dc Dec 08 12:17:06 angstrom: 03testlab  07yocto * r20f3f9d417 10testlab/beaglebone/eglibc/systemd-image/ (build-id installed-package-sizes.txt installed-packages.txt): beaglebone: systemd-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 118249f9ec841ce677fd12c36c2ca6bf20a068dc Dec 08 13:58:06 angstrom: 03testlab  07yocto * r355c10fdce 10testlab/beaglebone/eglibc/Cloud9-IDE/ (build-id installed-package-sizes.txt installed-packages.txt): beaglebone: Cloud9-IDE configured for angstrom v2011.12-core using branch angstrom-staging and revision 118249f9ec841ce677fd12c36c2ca6bf20a068dc Dec 08 14:18:28 angstrom: 03testlab  07yocto * r944ecc09c5 10testlab/beagleboard/eglibc/systemd-image/build-id: beagleboard: systemd-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 118249f9ec841ce677fd12c36c2ca6bf20a068dc Dec 08 14:38:47 angstrom: 03testlab  07yocto * r2b3b86ac62 10testlab/beagleboard/eglibc/systemd-GNOME-image/build-id: beagleboard: systemd-GNOME-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 118249f9ec841ce677fd12c36c2ca6bf20a068dc Dec 08 14:38:57 angstrom: 03testlab  07yocto * r77fbfd95fb 10testlab/beagleboard/eglibc/XFCE-NetworkManager-image/build-id: beagleboard: XFCE-NetworkManager-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 118249f9ec841ce677fd12c36c2ca6bf20a068dc Dec 08 17:00:32 angstrom: 03testlab  07yocto * r81ca941410 10testlab/omap4430_panda/eglibc/systemd-image/ (5 files): omap4430-panda: systemd-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 118249f9ec841ce677fd12c36c2ca6bf20a068dc Dec 08 18:33:47 I've followed the instructions on the web site for building angstrom and have built a kernel for a Pandaboard...one thing I noticed is that it's building version 2010_x but I see refrences to 2011_Y (where Y is variable)...is there a "newer version" I may want to build? Dec 08 20:22:22 angstrom: 03testlab  07yocto * rc94ba2fbeb 10testlab/beagleboard/eglibc/systemd-image/ (4 files): beagleboard: systemd-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 84cb57ea80280e47e91f1c7d891bae58c59b96b6 Dec 08 20:42:43 angstrom: 03testlab  07yocto * r2ce91615aa 10testlab/beagleboard/eglibc/efl-nodm-image/ (5 files): beagleboard: efl-nodm-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 84cb57ea80280e47e91f1c7d891bae58c59b96b6 Dec 08 21:03:04 angstrom: 03testlab  07yocto * r7287ad8769 10testlab/beagleboard/eglibc/systemd-GNOME-image/ (4 files): beagleboard: systemd-GNOME-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 84cb57ea80280e47e91f1c7d891bae58c59b96b6 Dec 08 21:03:14 angstrom: 03testlab  07yocto * r32a436fe5f 10testlab/beagleboard/eglibc/XFCE-NetworkManager-image/ (4 files): beagleboard: XFCE-NetworkManager-image configured for angstrom v2011.12-core using branch angstrom-staging and revision 84cb57ea80280e47e91f1c7d891bae58c59b96b6 Dec 09 00:32:38 So I have used the build script to build angstrom, but i tried to apply a patch for a camera driver, and it failed. It failed because it was missing a file it was trying to patch. Dec 09 00:33:05 The file is related to omap3 processor... so I assume I need to somehow specify a specific linux kernel for omap when i type the build command Dec 09 00:33:10 But I have no idea what to specify Dec 09 00:33:19 https://github.com/Aptina/BeagleBoard-xM/blob/master/MT9P031/Angstrom/README_MT9P031.txt is the driver Dec 09 00:43:00 !logs **** ENDING LOGGING AT Fri Dec 09 02:59:58 2011