• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Linux Stuff / General Linux questions / Re: Problem with cron on: October 26, 2009, 11:47:40 PM
I suspect I may have a oorexx bug here. strace via htop on the idling process reads:
futex(0x40160f18, FUTEX_WAIT_PRIVATE, 2, NULL
So it is waiting endlessly for another process to change a specific memory address. Since the idling process actually seems to be a child process of oorexx itself, created while executing the rexx script , I' ll put this case to the oorexx-authorities...

Thanks for your help so far. I really never heard of strace or the the /proc-vfs until now. I'm a bloody beginner on linux.


2  Linux Stuff / General Linux questions / Re: Problem with cron on: October 26, 2009, 10:49:07 AM
So the process is still there.
Yes, according to htop, it just sits there, apparently not running. After a SIGTERM it goes away and frees it's memory.
Does it have a log file (if not - can it have one).
Apparently not. I can only trace script execution, not the interpreter itself.
Have you checked on what files it has open (in /proc/<pid>/fd)?
I have now. /proc/(pid of rexx)/fd is empty.
Is it actually doing anything, or is it waiting on something?
The interpreted script exits fine. I have postfix/mutt installed (http://computingplugs.com/index.php/Postfix_and_Mutt), and after each execution I get mail from cron. So rexx really just sits there, apparently doing nothing.
Try running strace on it.
I'll do that, when I have more time at hand. But the plug is my first real experience with linux. Tracing programs is not what I'm used to do... :-)


BTW: Apart from this one problem, I think the plug is the best computer related investment I ever did... I'm running transmission, hiawatha with php and mysql, vsftpd, mediatomb, privoxy and squid on it, replacing a 100+ watts windows server machine. And it works really well.
3  Linux Stuff / General Linux questions / Problem with cron on: October 25, 2009, 11:10:04 AM

I compiled ooRexx (http://www.oorexx.org/) v4 on my SheevaPlug. Rexx programs work fine from the command line. But when I try to start a rexx-script via cron, after succesfully running, rexx doesn't exit. It stays in memory, on each run filling up my plug's precious memory with about 4 MB.

My plug has been updated with sheevaplug installer 1.0, booting from a sdcard.

I asked first in newsgroup comp.lang.rexx, but obviously this problem is unique. I suspect this is a linux problem on the plug. Anyone else had any problems like this?

Pages: [1]