PAUL SMITH WROTE:
> WELL, YOU SAID IT SEEMED TO BE RELATED TO RUNNING VIA
CRON. IT SEEMS
> UNLIKELY TO ME THAT IF THE SAME BUILD WITH THE SAME
AMOUNT OF
> PARALLELISM AND THE SAME COMMAND LINE RUNNING ON THE
SAME SERVER IN
> THE SAME FILESYSTEM WORKS PROPERLY WHEN YOU INVOKE IT
BY HAND AND
> BREAKS WHEN YOU RUN IT FROM CRON, THAT IT IS RELATED TO
THE FILESYSTEM
> TIMESTAMP SUPPORT.
I'M RESTARTING THIS THREAD - I'VE BEEN MAKING SOME PROGRESS.
THE PROBLEM I'M SEEING IS (SOMEHOW) DIRECTLY RELATED TO
OUTPUT TO
STDERR. ONE OF THE UTILITIES I'M USING IN MY JOBS PRODUCES
OUTPUT TO
BOTH STDOUT AND STDERR (5-6 LINES OF DIAGNOSTICS ETC.)
I WENT IN AND MADE SOME MINOR CHANGES IN JOB.C TO DEAL WITH
STDERR
OUTPUT.
AFTER THE CHILD HAS BEEN FORKED(), I OPEN TEMPORARY FILE AND
USE DUP2()
TO DIRECT STDERR OUTPUT THAT WAY - AND EVERYTHING SUDDENLY
WORKS!
ALL OF MY JOBS ARE RUN, AND THE OUTPUT IS ALSO NO LONGER
GARBLED NOR
TRUNCATED.
IT'S HARDLY A FIX FOR THE PROBLEM - I WOULD SORT OF PREFER
TO HAVE THE
STDERR OUTPUT PRESENT IN MY FINAL OUTPUT TOO, BUT IT'S NOT
CRITICAL, SO
AS A WORK-AROUND THIS WILL DO.
I'VE BEEN TRYING TO SPOT HOW & WHERE (IN JOB.C) STDOUT
IS BEING TREATED
DIFFERENTLY TO STDERR, BUT I HAVEN'T HAD ANY LUCK JUST YET.
/PER JESSEN, ZüRICH
_______________________________________________
HELP-MAKE MAILING LIST
HELP-MAKE GNU.ORG
HTTP://LISTS.GNU.ORG/MAILMAN/LISTINFO/HELP-MAKE
|